CVE-2026-2411Public exploit

Protected GATT value disclosure via wrong permission check

Published Aug 1, 2026 · Updated Aug 1, 2026

Incorrect authorization in Zephyr RTOS 2.6.0 through 4.4.1 allows physically proximate attackers to read protected GATT values via BLE notifications. When an application passes a Characteristic Declaration to the notify or indicate API, the Bluetooth host checks its fixed read permission instead of the following value attribute's encryption, authentication, or LESC requirements. Exposure requires a notify- or indicate-enabled characteristic with stronger value permissions than its writable CCC, and is limited to disclosure over an undersecured link.

CVSS severity6.5
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in Zephyr RTOS 2.6.0 through 4.4.1 allows physically proximate attackers to read protected GATT values via BLE notifications. When an application passes a Characteristic Declaration to the notify or indicate API, the Bluetooth host checks its fixed read permission instead of the following value attribute's encryption, authentication, or LESC requirements. Exposure requires a notify- or indicate-enabled characteristic with stronger value permissions than its writable CCC, and is limited to disclosure over an undersecured link.

The record

CVE
CVE-2026-2411
Published
Aug 1, 2026
Updated
Aug 1, 2026
Vendor
Zephyr Project
Product
Zephyr RTOS
Classifications
CWE-863
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 1, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 1, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=2.6.0 <4.5.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

Zephyr Project · Zephyr RTOSversion=2.6.0 <4.5.0

Published CVSS scores

6.5Zephyr ProjectCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo