CVE-2026-13199

MEDIUMPre-NVD 4.04.0
EchelonGraph scoreHIGH confidence

Score 4.0 from GitHub Security Advisory published 2026-07-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
4.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.0Exploit: None knownExposed: 0

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

EEPROM firmware on Raspberry Pi 5 and Compute Module 5 devices produced non-random KASLR and RNG seed values. This resulted in consistent kernel addresses across boots and devices, potentially making it easier to exploit other vulnerabilities. Additionally, the low-quality RNG seed may affect the quality of random numbers or delay booting while sufficient entropy is accumulated from other sources.

CVSS v3
4.0
EG Score
4.0(high)
EG Risk
18(Track)
EG Risk 18/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity40% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 7, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

pieeprom-2026-05-26: 2712: Make Pi 5 use the correct entropy source for kaslr-seed and rng-seed (latest)

Patch available: raspberrypi/rpi-eeprom v2026.05.17-2711-0138c0 (PR #841 merged 2026-05-26)

https://github.com/raspberrypi/rpi-eeprom/pull/841

Vendor Advisories for CVE-2026-13199(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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-26 12:42 UTCEG score recompute
  2. 2026-07-26 12:42 UTCGHSA enrichment
  3. 2026-07-25 14:17 UTCEPSS rescore
  4. 2026-07-24 14:17 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:05 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:30 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 22:54 UTCGHSA enrichment
  12. 2026-07-16 17:02 UTCEPSS rescore
  13. 2026-07-15 21:20 UTCGHSA enrichment
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-14 19:46 UTCGHSA enrichment
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 18:12 UTCGHSA enrichment
  19. 2026-07-13 06:12 UTCEPSS rescore
  20. 2026-07-12 16:38 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 15:04 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-10 13:30 UTCGHSA enrichment
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 9 more
  1. 2026-07-09 11:56 UTCGHSA enrichment
  2. 2026-07-08 15:15 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-08 10:22 UTCEG score recompute 1.10
  5. 2026-07-08 10:22 UTCGHSA enrichment
  6. 2026-07-07 13:53 UTCMITRE cvelistV5CVSS v3 → 4
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-07 08:48 UTCEG score recompute
  9. 2026-07-07 08:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13199?
CVE-2026-13199 is a medium vulnerability published on July 7, 2026. EEPROM firmware on Raspberry Pi 5 and Compute Module 5 devices produced non-random KASLR and RNG seed values. This resulted in consistent kernel addresses across boots and devices, potentially making it easier to exploit other vulnerabilities. Additionally, the low-quality RNG seed may affect the…
When was CVE-2026-13199 disclosed?
CVE-2026-13199 was first published in the National Vulnerability Database on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13199 actively exploited?
CVE-2026-13199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-13199?
CVE-2026-13199 has a CVSS v3.1 base score of 4.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13199, 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-2026-13199

Explore →

Is Your Infrastructure Affected by CVE-2026-13199?

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