Is there a public exploit for CVE-2026-18748?

No public exploit for CVE-2026-18748 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

How severe is CVE-2026-18748?

CVE-2026-18748 scores CVSS 3.5 (v3.1), rated low. EPSS puts the chance of exploitation in the next 30 days at 0.2%.

What does CVE-2026-18748 affect?

CVE-2026-18748 affects zephyrproject Zephyr.

3.5 Low

The Bluetooth Classic A2DP host stores a codec Information Element (IE) in struct bta2dpcodecie, a one-byte len field plus a fixed 8-byte…

CVE-2026-18748

The Bluetooth Classic A2DP host stores a codec Information Element (IE) in struct bta2dpcodecie, a one-byte len field plus a fixed 8-byte codecie[] array. When an AVDTP peer sent a codec IE longer than 8 bytes, a2dpprocessconfigind() in subsys/bluetooth/host/classic/a2dp.c copied only the first 8 bytes but assigned the full, attacker-chosen length to len, and then persisted that inconsistent structure into the application's struct bta2dpstream via stream->codecconfig. bta2dpgetconfigcb() and bta2dpsetconfigcb() had the same truncate-the-copy-but-keep-the-length pattern. Every later consumer trusts len. In particular the responder for an incoming AVDTP GETCONFIGURATION, a2dpgetconfigind(), executes netbufaddmem(rspbuf, &ep->stream->codecconfig.codecie[0], ep->stream->codecconfig.len), so a paired BR/EDR peer that first sends a SETCONFIGURATION carrying an oversized codec IE and then requests the configuration back causes the stack to read up to roughly 245 bytes past the end of the 8-byte array and transmit them in the response. codecconfig is the last member of struct bta2dpstream, so the read runs into memory adjacent to the application's stream object. The same inconsistency is…

Assessment

CVSS: 3.5 (v3.1)
Severity: Low
EPSS: 0.2% chance of exploitation in the next 30 days
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 21 October 2026
Last updated: 4 November 2026
Affected: zephyrproject · Zephyr
Assigner: zephyr

CVSS vectorCVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 3 + 2? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-18748