CVE-2026-18102

LOWPre-NVD 3.53.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 4 sources updated this week
3.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.5Exploit: 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 overwrite adjacent memory due to an integer underflow during bounds checking.

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

Published

August 19, 2026

Last Modified

August 20, 2026

References (1)

Vendor Advisories for CVE-2026-18102(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 10× in last 7d / 10× 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 17:35 UTCEG score recompute
  3. 2026-08-20 17:35 UTCGHSA enrichment
  4. 2026-08-20 16:36 UTCEG score recompute
  5. 2026-08-20 16:36 UTCGHSA enrichment
  6. 2026-08-20 13:25 UTCEG score recompute
  7. 2026-08-20 13:25 UTCGHSA enrichment
  8. 2026-08-19 21:19 UTCEG score recompute
  9. 2026-08-19 20:38 UTCEG score recompute
  10. 2026-08-19 20:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18102?
CVE-2026-18102 is a low vulnerability published on August 19, 2026. IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to overwrite adjacent memory due to an integer underflow during bounds checking.
When was CVE-2026-18102 disclosed?
CVE-2026-18102 was first published in the National Vulnerability Database on August 19, 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-18102 actively exploited?
CVE-2026-18102 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 86.6% of all scored CVEs.
What is the CVSS score of CVE-2026-18102?
CVE-2026-18102 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2026-18102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18102, 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-18102

Explore →

Is Your Infrastructure Affected by CVE-2026-18102?

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

Start Free Scan →Browse All CVEs