CVE-2026-18249: IBM i Is Affected By Multiple Vulnerabilities in IBM Java SDK and IBM Java Runtime
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to gain elevated privileges due to improper validation of pointers read from Java-controlled addresses.
- Published
- Aug 13, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-269
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.9
- CNA · ibm
- 8.4
- 1.5 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| ibm | i | cpe:2.3:o:ibm:i |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm i7.3
- ibm i7.4
- ibm i7.5
- ibm i7.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM i
- 7.6, 7.5, 7.4, 7.3affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-18193IBM i Is Affected By Multiple Vulnerabilities in IBM Java SDK and IBM Java Runtime40Plan
- CVE-2026-96119IBM i is Affected By An Improper Control of Code Generation Vulnerability in HTTP Server Administration GUI39Monitor
- CVE-2026-18221IBM i is Affected By Improper Authorization and Authentication Vulnerabilities in DDM / DRDA [, ]39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-18086Aug 13, 2026 · IBM i is Affected By Multiple Vulnerabilities in Java Secure Sockets Extension21Monitor
- ← EarlierCVE-2026-18101Aug 13, 2026 · IBM i is Affected By Multiple Vulnerabilities in WebSphere Application Server Liberty35Monitor
- Later →CVE-2026-18509Aug 13, 2026 · IBM i is Affected By A Prvilege Escalation Vulnerability []28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-181930 days apartIBM i Is Affected By Multiple Vulnerabilities in IBM Java SDK and IBM Java Runtime40Plan
- CVE-2026-172761 days apartIBM i is Affected By Multiple Vulnerabilities in Navigator for i39Monitor
- CVE-2026-167220 days apartIBM i is Affected By An Unauthorized Privileges Vulnerability in SQL []35Monitor
- CVE-2026-181010 days apartIBM i is Affected By Multiple Vulnerabilities in WebSphere Application Server Liberty35Monitor
- CVE-2026-170821 days apartIBM i is Affected By Multiple Vulnerabilities in the Debug Server35Monitor
- CVE-2026-187131 days apartIBM i is Affected By Multiple Vulnerabilities in Navigator for i35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- low · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- Low
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRole
rules:
- apiGroups: ["*"]
resources: ["*"]
verbs: ["*"]Fixed
kind: Role
metadata:
namespace: lodos-system
rules:
- apiGroups: ["apps"]
resources: ["deployments"]
verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.