CVE-2026-56115

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 5.3 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-06-23) is not newer than that change (2026-10-25), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-38494 (ENISA EUVD) · GHSA-vhmp-9f3g-3f36 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

Bootimus through 0.1.70 contains a broken access control vulnerability that allows authenticated low-privileged users to perform administrative actions by exploiting missing role enforcement in the JWTMiddleware function in internal/auth/auth.go, which validates JWT tokens and account status but fails to inspect the is_admin flag. Attackers can send requests to any endpoint under the /api/users path to create new administrator accounts or reset administrator passwords, thereby gaining full control of the server and the ability to modify boot menus and installation scripts served to PXE clients.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (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

June 23, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

dhcpcd Stack Out-of-Bounds Write in dhcp6_makemessage() | Advisories | VulnCheck

https://www.vulncheck.com/advisories/dhcpcd-stack-out-of-bounds-write-in-dhcp6-makemessage
GitHub commit

commit 2f00c7bfc408 (NetworkConfiguration/dhcpcd)

Fix landed in NetworkConfiguration/dhcpcd commit 2f00c7bfc408 — awaiting tagged release

https://github.com/NetworkConfiguration/dhcpcd/commit/2f00c7bfc408b6582d331932dfa47829c4819029

Vendor Advisories for CVE-2026-56115(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 45× 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 100 of 257 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. None are among the latest 100 rows. The 157 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-56115?
CVE-2026-56115 is a high-severity vulnerability; its CVE record was published on June 23, 2026. Bootimus through 0.1.70 contains a broken access control vulnerability that allows authenticated low-privileged users to perform administrative actions by exploiting missing role enforcement in the JWTMiddleware function in internal/auth/auth.go, which validates JWT tokens and account status but…
When was the CVE record for CVE-2026-56115 published?
The CVE record for CVE-2026-56115 was published on June 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-56115 actively exploited?
CVE-2026-56115 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56115?
CVE-2026-56115 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56115?
An upstream fix for CVE-2026-56115 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-56115 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-56115

Explore →

Is Your Infrastructure Affected by CVE-2026-56115?

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