Public proof of conceptFix available

CVE-2019-9506

Q: Is CVE-2019-9506 actively exploited?

Active exploitation of CVE-2019-9506 has not been confirmed. Its EPSS score was 2.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2019-9506?

CVE-2019-9506 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

A public proof of concept exists; no exploitation attested.

Published2019-08-14
Fixed in9.1.0.172\(c432e2r5p1\) · 9.1.0.171\(c10e2r3p1\) · 9.1.0.170\(c185e2r5p1\) · 9.1.0.170\(c636e2r3p1\) · 9.1.0.155\(c10e2r3p1\) · 9.1.0.154\(c185e2r5p1\)
WeaknessCWE-310 · CWE-327

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The Bluetooth BR/EDR specification up to and including version 5.1 permits sufficiently low encryption key length and does not prevent an attacker from influencing the key length negotiation. This allows practical brute-force attacks (aka "KNOB") that can decrypt traffic and inject arbitrary ciphertext without the victim noticing.

Timeline

dates in UTC

2019-08-1417:15CVE publishedNVD
2026-10-2319:23First public proof of conceptPoC-in-GitHub

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-9506?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-9506?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Huawei honor 20 pro firmwareversion to verify

Branch	Affected	Fixed in	Source
9.1	< 9.1.0.172\(c432e2r5p1\)	9.1.0.172\(c432e2r5p1\)	NVD
9.1	< 9.1.0.171\(c10e2r3p1\)	9.1.0.171\(c10e2r3p1\)	NVD
9.1	< 9.1.0.170\(c185e2r5p1\)	9.1.0.170\(c185e2r5p1\)	NVD
9.1	< 9.1.0.170\(c636e2r3p1\)	9.1.0.170\(c636e2r3p1\)	NVD
9.1	< 9.1.0.155\(c10e2r3p1\)	9.1.0.155\(c10e2r3p1\)	NVD
9.1	< 9.1.0.154\(c185e2r5p1\)	9.1.0.154\(c185e2r5p1\)	NVD
9.1	< 9.1.0.154\(c432e2r5p1\)	9.1.0.154\(c432e2r5p1\)	NVD
9.1	< 9.1.0.154\(c636e2r3p1\)	9.1.0.154\(c636e2r3p1\)	NVD

Huawei emily-l29c firmwareversion to verify

Branch	Affected	Fixed in	Source
9.1	< 9.1.0.328\(c432e7r1p11t8\)	9.1.0.328\(c432e7r1p11t8\)	NVD
9.1	< 9.1.0.326\(c635e2r1p11t8\)	9.1.0.326\(c635e2r1p11t8\)	NVD
9.1	< 9.1.0.325\(c185e2r1p12t8\)	9.1.0.325\(c185e2r1p12t8\)	NVD
9.1	< 9.1.0.325\(c636e7r1p13t8\)	9.1.0.325\(c636e7r1p13t8\)	NVD
9.1	< 9.1.0.311\(c461e2r1p11t8\)	9.1.0.311\(c461e2r1p11t8\)	NVD
8.1	= 8.1.0.156\(c605\)	no fix published	NVD

Huawei figo-l31 firmwareversion to verify

Branch	Affected	Fixed in	Source
9.1	< 9.1.0.165\(c10e8r1p5t8\)	9.1.0.165\(c10e8r1p5t8\)	NVD
9.1	< 9.1.0.158\(c432e8r1p5t8\)	9.1.0.158\(c432e8r1p5t8\)	NVD
9.1	< 9.1.0.137\(c33e8r1p5t8\)	9.1.0.137\(c33e8r1p5t8\)	NVD
9.1	< 9.1.0.137\(c530e8r1p5t8\)	9.1.0.137\(c530e8r1p5t8\)	NVD
9.1	< 9.1.0.122\(c09e7r1p5t8\)	9.1.0.122\(c09e7r1p5t8\)	NVD
8.0	= 8.0.0.122d\(c652\)	no fix published	NVD

144 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update Huawei honor 20 pro firmware to 9.1.0.172\(c432e2r5p1\) · 9.1.0.171\(c10e2r3p1\) · 9.1.0.170\(c185e2r5p1\) · 9.1.0.170\(c636e2r3p1\) · 9.1.0.155\(c10e2r3p1\) · 9.1.0.154\(c185e2r5p1\) · 9.1.0.154\(c432e2r5p1\) · 9.1.0.154\(c636e2r3p1\)

Detection

read 2026-10-23 19:23 UTC

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: 1 repository, unverifiedfrancozappa/knob

Sources

NVDCVSS 3.18.1read 2026-10-23
CNACVSS 3.07.6read 2026-10-23
NVDCVSS 2.04.8read 2026-10-23
CNAweakness (CWE)CWE-310read 2026-10-23
NVDweakness (CWE)CWE-327read 2026-10-23
FIRST EPSSEPSS score2.7 %2026-10-22
PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Published: 2019-08-14
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2019-9506?

Is CVE-2019-9506 actively exploited?

Active exploitation of CVE-2019-9506 has not been confirmed. Its EPSS score was 2.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-9506?

CVE-2019-9506 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database