CVE-2026-10772 ** DUPLICATE ** This CVE Record has been rejected by the Zephyr Project CNA.
Not scored
Updated
Check this codebase for CVE-2026-10772 and fix it if it is affected.
What it is: CVE-2026-10772 is a vulnerability.
Exploitation: There is no known exploitation of CVE-2026-10772 in the wild and no public exploit code.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-10772/ (Markdown: https://insights.sbomify.com/CVE-2026-10772/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-10772?
CVE-2026-10772 is a vulnerability.
Official description
** DUPLICATE ** This CVE Record has been rejected by the Zephyr Project CNA. CVE-2026-10772 was assigned to a vulnerability already covered by CVE-2026-2411, which was assigned earlier for the same defect: the Bluetooth GATT notify/indicate paths check the permissions of the Characteristic Declaration attribute rather than the Characteristic Value attribute, so the encryption/authentication requirements configured on the value are not enforced. Both identifiers describe the same root cause in subsys/bluetooth/host/gatt.c, fixed by the same commit (c3386f92fe81bd10dc23e6a115e6a80a7d863546). Use CVE-2026-2411 instead.
Which versions are affected by CVE-2026-10772?
How do I fix CVE-2026-10772?
No fix has been published for CVE-2026-10772 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-10772 being exploited?
There is no known exploitation of CVE-2026-10772 in the wild and no public exploit code.
Sources
Also known as GHSA-g8gc-4j8m-395r.