CVE-2019-15126

LOWNVD 3.13.1
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under NVD CVSS v3. EPSS exploit probability: 7.7%, top 6% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
3.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 8%CVSS: 3.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An issue was discovered on Broadcom Wi-Fi client devices. Specifically timed and handcrafted traffic can cause internal errors (related to state transitions) in a WLAN device that lead to improper layer 2 Wi-Fi encryption with a consequent possibility of information disclosure over the air for a discrete set of traffic, a different vulnerability than CVE-2019-9500, CVE-2019-9501, CVE-2019-9502, and CVE-2019-9503.

CVSS v3
3.1
EG Score
3.1(medium)
EG Risk
EPSS
94.0%
KEV
Not listed

Published

February 5, 2020

Last Modified

November 21, 2024

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-22 22:20 UTCEG score recompute
  2. 2026-07-22 14:05 UTCEPSS rescore
  3. 2026-07-21 15:22 UTCEPSS rescore
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-20 17:04 UTCEPSS rescore
  6. 2026-07-19 14:28 UTCEPSS rescore
  7. 2026-07-19 14:28 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-18 10:01 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-16 16:59 UTCEPSS rescore
  13. 2026-07-15 16:55 UTCEPSS rescore
  14. 2026-07-13 22:27 UTCEPSS rescore
  15. 2026-07-13 06:10 UTCEPSS rescore
  16. 2026-07-13 06:10 UTCEPSS rescore
  17. 2026-07-12 05:43 UTCEPSS rescore
  18. 2026-07-11 08:24 UTCEPSS rescore
  19. 2026-07-09 19:06 UTCEPSS rescore
  20. 2026-07-08 15:11 UTCEPSS rescore
  21. 2026-07-07 13:42 UTCEPSS rescore
  22. 2026-07-06 16:25 UTCEPSS rescore
  23. 2026-07-06 02:20 UTCEPSS rescore
  24. 2026-07-05 02:27 UTCEPSS rescore
  25. 2026-07-04 06:28 UTCEPSS rescore
Show 61 more
  1. 2026-07-04 06:28 UTCEPSS rescore
  2. 2026-07-02 16:56 UTCEPSS rescore
  3. 2026-07-01 15:03 UTCEPSS rescore
  4. 2026-07-01 15:03 UTCEPSS rescore
  5. 2026-06-30 23:20 UTCEPSS rescore
  6. 2026-06-30 23:20 UTCEPSS rescore
  7. 2026-06-29 14:03 UTCEPSS rescore
  8. 2026-06-28 14:04 UTCEPSS rescore
  9. 2026-06-28 04:54 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:06 UTCEPSS rescore
  12. 2026-06-27 03:06 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:03 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-21 14:54 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 01:57 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
  26. 2026-06-15 17:45 UTCEPSS rescore
  27. 2026-06-14 23:15 UTCEPSS rescore
  28. 2026-06-14 23:15 UTCEPSS rescore
  29. 2026-06-13 22:58 UTCEPSS rescore
  30. 2026-06-12 23:09 UTCEPSS rescore
  31. 2026-06-11 13:58 UTCEPSS rescore
  32. 2026-06-11 13:58 UTCEPSS rescore
  33. 2026-06-10 22:16 UTCEPSS rescore
  34. 2026-06-10 13:19 UTCEPSS rescore
  35. 2026-06-08 14:15 UTCEPSS rescore
  36. 2026-06-08 14:14 UTCEPSS rescore
  37. 2026-06-07 15:23 UTCEPSS rescore
  38. 2026-06-07 15:22 UTCEPSS rescore
  39. 2026-06-06 13:45 UTCEPSS rescore
  40. 2026-06-06 13:45 UTCEPSS rescore
  41. 2026-06-05 22:45 UTCEPSS rescore
  42. 2026-06-05 22:45 UTCEPSS rescore
  43. 2026-06-05 06:08 UTCEPSS rescore
  44. 2026-06-05 06:08 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-04 13:10 UTCEPSS rescore
  47. 2026-06-02 20:11 UTCEPSS rescore
  48. 2026-06-01 13:50 UTCEPSS rescore
  49. 2026-06-01 13:50 UTCEPSS rescore
  50. 2026-05-31 22:29 UTCEPSS rescore
  51. 2026-05-31 22:29 UTCEPSS rescore
  52. 2026-05-31 00:14 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-29 13:42 UTCEPSS rescore
  55. 2026-05-28 13:43 UTCEPSS rescore
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 08:15 UTCEG score recompute
  58. 2026-05-27 08:15 UTCVendor advisory
  59. 2026-05-27 08:15 UTCGHSA enrichment
  60. 2026-05-26 13:42 UTCEPSS rescore
  61. 2026-05-26 13:42 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-48233
    First seen Mar 18, 2020

    Broadcom Wi-Fi Devices - 'KR00K Information Disclosure

    Open source ↗
  • GitHub PoCakabe1/kr00ker
    First seen Mar 18, 2020

    An experimental script PoC for Kr00k vulnerability (CVE-2019-15126)

    Open source ↗
  • GitHub PoChexway/r00kie-kr00kie
    First seen Mar 13, 2020

    PoC exploit for the CVE-2019-15126 kr00k vulnerability

    Open source ↗
  • GitHub PoC0x13enny/kr00k
    First seen Mar 9, 2020

    PoC of CVE-2019-15126 kr00k vulnerability

    Open source ↗

Frequently asked(5)

What is CVE-2019-15126?
CVE-2019-15126 is a low vulnerability published on February 5, 2020. An issue was discovered on Broadcom Wi-Fi client devices. Specifically timed and handcrafted traffic can cause internal errors (related to state transitions) in a WLAN device that lead to improper layer 2 Wi-Fi encryption with a consequent possibility of information disclosure over the air for a…
When was CVE-2019-15126 disclosed?
CVE-2019-15126 was first published in the National Vulnerability Database on February 5, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-15126 actively exploited?
CVE-2019-15126 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-15126?
CVE-2019-15126 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2019-15126?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-15126, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-15126

Explore →

Is Your Infrastructure Affected by CVE-2019-15126?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.