CVE-2026-16693

MEDIUMNVD 4.94.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.9 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 97% 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 — 3 sources updated this week
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0

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

IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to obtain sensitive information due to the use of hardcoded cryptographic constants to obfuscate encryption keys.

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

Published

September 4, 2026

Last Modified

September 8, 2026

Advisory Details (1)

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

Security Bulletin: IBM i is Affected By Cryptographic Algorithm Weakness in DCM [CVE-2026-16693]

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

Vendor Advisories for CVE-2026-16693(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 18× 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-09-19 16:00 UTCEG score recompute
  2. 2026-09-19 16:00 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 18:18 UTCGHSA enrichment
  5. 2026-09-17 20:22 UTCEG score recompute
  6. 2026-09-17 20:22 UTCGHSA enrichment
  7. 2026-09-16 21:47 UTCEG score recompute
  8. 2026-09-16 21:47 UTCGHSA enrichment
  9. 2026-09-16 14:07 UTCEPSS rescore
  10. 2026-09-16 05:14 UTCEPSS rescore
  11. 2026-09-16 00:07 UTCEG score recompute
  12. 2026-09-16 00:07 UTCGHSA enrichment
  13. 2026-09-15 02:26 UTCGHSA enrichment
  14. 2026-09-14 04:45 UTCEG score recompute
  15. 2026-09-14 04:45 UTCGHSA enrichment
  16. 2026-09-13 16:46 UTCEPSS rescore
  17. 2026-09-13 07:05 UTCEG score recompute
  18. 2026-09-13 07:05 UTCGHSA enrichment
  19. 2026-09-12 15:00 UTCEPSS rescore
  20. 2026-09-12 09:25 UTCEG score recompute
  21. 2026-09-12 09:25 UTCGHSA enrichment
  22. 2026-09-11 14:52 UTCEPSS rescore
  23. 2026-09-11 11:45 UTCEG score recompute
  24. 2026-09-11 11:45 UTCGHSA enrichment
  25. 2026-09-11 09:36 UTCEPSS rescore
Show 19 more
  1. 2026-09-10 13:46 UTCEG score recompute
  2. 2026-09-10 13:46 UTCGHSA enrichment
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-09 16:06 UTCGHSA enrichment
  5. 2026-09-08 18:16 UTCEG score recompute▲ 0.50
  6. 2026-09-08 18:16 UTCGHSA enrichment
  7. 2026-09-08 17:30 UTCNVD updateCVSS v3 → 4.9
  8. 2026-09-08 15:13 UTCGHSA enrichment
  9. 2026-09-08 09:58 UTCGHSA enrichment
  10. 2026-09-07 11:41 UTCGHSA enrichment
  11. 2026-09-06 13:59 UTCGHSA enrichment
  12. 2026-09-05 16:19 UTCEG score recompute
  13. 2026-09-05 16:19 UTCGHSA enrichment
  14. 2026-09-04 18:39 UTCEG score recompute
  15. 2026-09-04 18:39 UTCGHSA enrichment
  16. 2026-09-04 17:35 UTCEG score recompute
  17. 2026-09-04 17:26 UTCEG score recompute
  18. 2026-09-04 16:44 UTCEG score recompute
  19. 2026-09-04 16:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16693?
CVE-2026-16693 is a medium vulnerability published on September 4, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to obtain sensitive information due to the use of hardcoded cryptographic constants to obfuscate encryption keys.
When was CVE-2026-16693 disclosed?
CVE-2026-16693 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16693 actively exploited?
CVE-2026-16693 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-16693?
CVE-2026-16693 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-16693?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16693, 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-16693

Explore →

Is Your Infrastructure Affected by CVE-2026-16693?

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

Start Free Scan →Browse All CVEs