CVE-2026-17081

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: None knownExposed: 0

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

IBM Db2 Mirror for i 7.4, 7.5, and 7.6 could allow a remote attacker to write arbitrary files due to improper limitation of a pathname to a restricted directory.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

August 14, 2026

Last Modified

August 20, 2026

Advisory Details (1)

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

Security Bulletin: IBM Db2 Mirror for i is affected by multiple vulnerabilities

https://www.ibm.com/support/pages/node/7283359

Vendor Advisories for CVE-2026-17081(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 33× in last 7d / 33× 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:55 UTCEPSS rescore
  2. 2026-08-20 21:42 UTCEG score recompute
  3. 2026-08-20 21:42 UTCGHSA enrichment
  4. 2026-08-20 21:42 UTCNVD updateCVSS v3 → 7.5
  5. 2026-08-20 13:57 UTCGHSA enrichment
  6. 2026-08-20 07:42 UTCGHSA enrichment
  7. 2026-08-19 18:50 UTCEG score recompute
  8. 2026-08-19 18:50 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 05:57 UTCGHSA enrichment
  11. 2026-08-18 17:02 UTCEG score recompute
  12. 2026-08-18 17:02 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 03:25 UTCEG score recompute
  15. 2026-08-18 03:24 UTCGHSA enrichment
  16. 2026-08-18 02:42 UTCEG score recompute
  17. 2026-08-18 02:41 UTCGHSA enrichment
  18. 2026-08-18 01:30 UTCEG score recompute
  19. 2026-08-18 01:30 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 12:38 UTCGHSA enrichment
  22. 2026-08-16 23:46 UTCEG score recompute
  23. 2026-08-16 23:46 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 10:54 UTCEG score recompute
Show 8 more
  1. 2026-08-16 10:54 UTCGHSA enrichment
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 22:02 UTCGHSA enrichment
  4. 2026-08-15 09:10 UTCEG score recompute
  5. 2026-08-15 09:10 UTCGHSA enrichment
  6. 2026-08-14 20:18 UTCEG score recompute
  7. 2026-08-14 19:39 UTCEG score recompute
  8. 2026-08-14 19:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17081?
CVE-2026-17081 is a high vulnerability published on August 14, 2026. IBM Db2 Mirror for i 7.4, 7.5, and 7.6 could allow a remote attacker to write arbitrary files due to improper limitation of a pathname to a restricted directory.
When was CVE-2026-17081 disclosed?
CVE-2026-17081 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17081 actively exploited?
CVE-2026-17081 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.2% of all scored CVEs.
What is the CVSS score of CVE-2026-17081?
CVE-2026-17081 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-17081?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17081, 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-17081

Explore →

Is Your Infrastructure Affected by CVE-2026-17081?

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

Start Free Scan →Browse All CVEs