CVE-2026-9031

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% 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, secondary
Trending — 3 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 input validation vulnerability exists in the HTTP-WRITEOEM handler due to insufficient validation of user-supplied data before it is processed by internal flash-write handling logic.

Successful exploitation may cause httpd process or device to crash, resulting in loss of access to the web interface and a denial-of-service condition.

CVSS v3
6.8
EG Score
6.8(medium)
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
6%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 18, 2026

Advisory Details (3)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

Security Advisory: Multiple Vulnerabilities in Archer A6 (CVE-2026-9030 & CVE-2026-9031) | TP-Link

https://www.tp-link.com/en/support/faq/5234/

Vendor Advisories for CVE-2026-9031(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 21× in last 7d / 44× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 14:40 UTCEG score recompute
  3. 2026-08-20 14:40 UTCGHSA enrichment
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-19 15:07 UTCGHSA enrichment
  6. 2026-08-18 15:34 UTCEG score recompute
  7. 2026-08-18 15:34 UTCGHSA enrichment
  8. 2026-08-18 13:49 UTCEPSS rescore
  9. 2026-08-17 16:31 UTCEG score recompute
  10. 2026-08-17 16:31 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:50 UTCEG score recompute
  13. 2026-08-16 16:50 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:15 UTCEPSS rescore
  17. 2026-08-15 17:18 UTCEG score recompute
  18. 2026-08-15 17:18 UTCGHSA enrichment
  19. 2026-08-15 01:31 UTCEPSS rescore
  20. 2026-08-14 17:45 UTCEG score recompute
  21. 2026-08-14 17:45 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 18:09 UTCGHSA enrichment
  24. 2026-08-12 18:37 UTCEG score recompute
  25. 2026-08-12 18:37 UTCGHSA enrichment
Show 19 more
  1. 2026-08-12 13:51 UTCEPSS rescore
  2. 2026-08-11 19:05 UTCEG score recompute
  3. 2026-08-11 19:05 UTCGHSA enrichment
  4. 2026-08-11 13:43 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 19:28 UTCEG score recompute
  7. 2026-08-10 19:28 UTCGHSA enrichment
  8. 2026-08-10 18:35 UTCEG score recompute
  9. 2026-08-10 18:35 UTCGHSA enrichment
  10. 2026-08-09 20:36 UTCEG score recompute
  11. 2026-08-09 20:36 UTCGHSA enrichment
  12. 2026-08-09 13:47 UTCEPSS rescore
  13. 2026-08-08 21:04 UTCEG score recompute
  14. 2026-08-08 21:04 UTCGHSA enrichment
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-07 21:32 UTCEG score recompute
  17. 2026-08-07 21:32 UTCGHSA enrichment
  18. 2026-08-07 20:47 UTCEG score recompute
  19. 2026-08-07 20:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-9031?
CVE-2026-9031 is a medium vulnerability published on August 7, 2026. An input validation vulnerability exists in the HTTP-WRITEOEM handler due to insufficient validation of user-supplied data before it is processed by internal flash-write handling logic. Successful exploitation may cause httpd process or device to crash, resulting in loss of access to the web…
When was CVE-2026-9031 disclosed?
CVE-2026-9031 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9031 actively exploited?
CVE-2026-9031 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 94.0% of all scored CVEs.
What is the CVSS score of CVE-2026-9031?
CVE-2026-9031 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-9031?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9031, 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-9031

Explore →

Is Your Infrastructure Affected by CVE-2026-9031?

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