CVE-2026-29007

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 5.3 from GitHub Security Advisory published 2026-07-08. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.3Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists u-boot versions up to and including 2026.04-rc3 as affected. No release containing a fix is confirmed on record.

U-Boot through 2026.04-rc3 contains an out-of-bounds read vulnerability in tcp_rx_state_machine() (net/tcp.c) when CONFIG_PROT_TCP is enabled, allowing remote attackers to read beyond TCP segment boundaries by crafting a malicious packet with a mismatched IP total length and TCP data offset field. Attackers can send a packet with an IP total length of 40 bytes and a TCP data offset claiming 60 bytes of header to cause tcp_parse_options() to read 40 bytes past the end of the TCP segment, potentially corrupting connection state variables such as rmt_win_scale and rmt_timestamp to disrupt TCP window calculations.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

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 (value × EchelonGraph’s weight)
Severity53% × 45%
The EG Score, 5.3 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 8, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No fix on record yet.
Web page

U-Boot 2026.04-rc3 Out-of-Bounds Read in tcp_rx_state_machine via tcp.c | Advisories | VulnCheck

https://www.vulncheck.com/advisories/u-boot-rc3-out-of-bounds-read-in-tcp-rx-state-machine-via-tcp-c
Web page

Das U-Boot: The Universal Boot Loader

https://u-boot.org/
Web page

Coordinated Vulnerability Disclosure - U-Boot Multiple Vulnerabilities (3)

https://lists.denx.de/pipermail/u-boot/2026-May/617853.html

Vendor Advisories for CVE-2026-29007(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2021.01+dfsg-5 ... 2025.01-3.2 (53 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2023.01+dfsg-2 ... 2025.01-3.2 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2025.01-3, 2025.01-3+deb13u1, 2025.01-3.1, 2025.01-3.2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2025.01-3, 2025.01-3.1, 2025.01-3.2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 184 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 89 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-10-12 16:16 UTCEG score recompute
  5. 2026-10-11 19:58 UTCEG score recompute
  6. 2026-10-11 17:12 UTCEG score recompute
  7. 2026-10-11 14:41 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-01 16:11 UTCEG score recompute
  19. 2026-10-01 16:11 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-09-28 13:22 UTCEG score recompute
  23. 2026-09-28 13:22 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  24. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
Show 70 more
  1. 2026-09-24 11:48 UTCEG score recompute
  2. 2026-09-24 11:48 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  3. 2026-09-23 06:10 UTCEG score recompute
  4. 2026-09-23 06:10 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  5. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  6. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  7. 2026-09-18 05:43 UTCEG score recompute
  8. 2026-09-18 05:43 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  9. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-09-14 11:15 UTCEG score recompute
  13. 2026-09-14 11:15 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  14. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  15. 2026-09-13 08:25 UTCEG score recompute
  16. 2026-09-13 08:25 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  17. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  18. 2026-09-12 03:35 UTCEG score recompute
  19. 2026-09-12 03:35 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  20. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  23. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  25. 2026-09-05 22:48 UTCEG score recompute
  26. 2026-09-05 22:48 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  27. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  28. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  29. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  30. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  31. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  32. 2026-08-30 07:33 UTCEG score recompute
  33. 2026-08-30 07:33 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  34. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  35. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  36. 2026-08-27 21:50 UTCEG score recompute
  37. 2026-08-27 21:50 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  38. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  39. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  40. 2026-08-26 08:24 UTCEG score recompute
  41. 2026-08-26 08:24 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  42. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  43. 2026-08-25 00:24 UTCEG score recompute
  44. 2026-08-25 00:24 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  45. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-08-23 22:19 UTCEG score recompute
  47. 2026-08-23 22:19 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  49. 2026-08-22 20:01 UTCEG score recompute
  50. 2026-08-22 20:01 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-08-21 17:55 UTCEG score recompute
  53. 2026-08-21 17:55 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  54. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  55. 2026-08-20 15:50 UTCEG score recompute
  56. 2026-08-20 15:50 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  57. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  58. 2026-08-19 13:46 UTCEG score recompute
  59. 2026-08-19 13:46 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  61. 2026-08-18 11:42 UTCEG score recompute
  62. 2026-08-18 11:42 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  63. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  64. 2026-08-17 09:37 UTCEG score recompute
  65. 2026-08-17 09:37 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  67. 2026-08-16 07:33 UTCEG score recompute
  68. 2026-08-16 07:33 UTCGHSA enrichmentGHSA-572m-4pr8-48pj · GitHub CVSS 5.3
  69. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  70. 2026-08-15 05:29 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-29007?
CVE-2026-29007 is a medium-severity vulnerability; its CVE record was published on July 8, 2026. U-Boot through 2026.04-rc3 contains an out-of-bounds read vulnerability in tcprxstatemachine() (net/tcp.c) when CONFIGPROTTCP is enabled, allowing remote attackers to read beyond TCP segment boundaries by crafting a malicious packet with a mismatched IP total length and TCP data offset field.…
When was CVE-2026-29007 made public?
CVE-2026-29007 was made public on May 8, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-29007 actively exploited?
CVE-2026-29007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29007?
CVE-2026-29007 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-29007?
No fix for CVE-2026-29007 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists u-boot versions up to and including 2026.04-rc3 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-29007 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-29007

Explore →

Is Your Infrastructure Affected by CVE-2026-29007?

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

Book a Demo →Browse All CVEs