CVE-2026-80253

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. a secondary CVSS source baseline 6.8; sources differ by 0.0.

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

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

An improper physical access control issue exists in ShizenBox2 (dev-conf). If exploited, an attacker with physical access to the product may execute bootloader commands without authentication.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 3, 2026

Advisory Details (2)

Auto-updated Sep 3, 2026
No patch confirmed yet.
generic

JVN#91715694: Multiple vulnerabilities in ShizenBox2

https://jvn.jp/en/jp/JVN91715694/
generic
https://www.se-digital.net/wp-content/uploads/2026/08/CVE-2026-80253.pdf

Vendor Advisories for CVE-2026-80253(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 19× in last 7d / 19× 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-09-08 22:01 UTCEPSS rescore
  2. 2026-09-08 09:59 UTCEG score recompute
  3. 2026-09-08 09:59 UTCGHSA enrichment
  4. 2026-09-07 11:29 UTCEG score recompute
  5. 2026-09-07 11:29 UTCGHSA enrichment
  6. 2026-09-06 13:48 UTCEPSS rescore
  7. 2026-09-06 13:01 UTCEG score recompute
  8. 2026-09-06 13:01 UTCGHSA enrichment
  9. 2026-09-05 15:31 UTCEPSS rescore
  10. 2026-09-05 14:35 UTCGHSA enrichment
  11. 2026-09-04 16:09 UTCEG score recompute
  12. 2026-09-04 16:08 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 17:39 UTCEG score recompute
  15. 2026-09-03 17:39 UTCGHSA enrichment
  16. 2026-09-03 14:29 UTCEG score recompute
  17. 2026-09-03 13:15 UTCEG score recompute
  18. 2026-09-03 08:59 UTCEG score recompute
  19. 2026-09-03 08:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80253?
CVE-2026-80253 is a medium vulnerability published on September 3, 2026. An improper physical access control issue exists in ShizenBox2 (dev-conf). If exploited, an attacker with physical access to the product may execute bootloader commands without authentication.
When was CVE-2026-80253 disclosed?
CVE-2026-80253 was first published in the National Vulnerability Database on September 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80253 actively exploited?
CVE-2026-80253 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 74.2% of all scored CVEs.
What is the CVSS score of CVE-2026-80253?
CVE-2026-80253 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-80253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80253, 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-80253

Explore →

Is Your Infrastructure Affected by CVE-2026-80253?

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

Start Free Scan →Browse All CVEs