CVE-2026-16480

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is affected by an improper authorization vulnerability in the certain command, allowing a non-privileged user to bypass authority checks and modify database catalog data.

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

Published

August 12, 2026

Last Modified

August 18, 2026

Advisory Details (1)

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

Security Bulletin: IBM® Db2® is affected by an improper authorization vulnerability in the certain command, allowing a non-privileged user to bypass authority checks and modify database catalog data. (CVE-2026-16480)

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

Vendor Advisories for CVE-2026-16480(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 26× in last 7d / 35× 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-21 03:56 UTCEG score recompute
  2. 2026-08-21 03:55 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:48 UTCGHSA enrichment
  5. 2026-08-20 05:41 UTCGHSA enrichment
  6. 2026-08-19 18:33 UTCEG score recompute
  7. 2026-08-19 18:33 UTCGHSA enrichment
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 06:21 UTCGHSA enrichment
  10. 2026-08-18 19:04 UTCEG score recompute▲ 2.80
  11. 2026-08-18 19:04 UTCGHSA enrichment
  12. 2026-08-18 19:03 UTCNVD updateCVSS v3 → 7.1 · severity → HIGH
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-18 11:12 UTCEG score recompute
  15. 2026-08-18 11:11 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 13:07 UTCGHSA enrichment
  18. 2026-08-16 15:06 UTCEG score recompute
  19. 2026-08-16 15:06 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 17:05 UTCEG score recompute
  23. 2026-08-15 17:05 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 19:03 UTCEG score recompute
Show 10 more
  1. 2026-08-14 19:03 UTCGHSA enrichment
  2. 2026-08-13 22:00 UTCEPSS rescore
  3. 2026-08-13 21:01 UTCGHSA enrichment
  4. 2026-08-13 14:24 UTCEG score recompute
  5. 2026-08-13 14:24 UTCGHSA enrichment
  6. 2026-08-13 13:56 UTCEG score recompute
  7. 2026-08-13 13:56 UTCGHSA enrichment
  8. 2026-08-12 21:20 UTCEG score recompute
  9. 2026-08-12 21:01 UTCEG score recompute
  10. 2026-08-12 21:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16480?
CVE-2026-16480 is a high vulnerability published on August 12, 2026. IBM Db2 11.5.0 through 11.5.9, and 12.1.0 through 12.1.5 is affected by an improper authorization vulnerability in the certain command, allowing a non-privileged user to bypass authority checks and modify database catalog data.
When was CVE-2026-16480 disclosed?
CVE-2026-16480 was first published in the National Vulnerability Database on August 12, 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-16480 actively exploited?
CVE-2026-16480 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 73.5% of all scored CVEs.
What is the CVSS score of CVE-2026-16480?
CVE-2026-16480 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-16480?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16480, 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-16480

Explore →

Is Your Infrastructure Affected by CVE-2026-16480?

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

Start Free Scan →Browse All CVEs