CVE-2026-6936
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM i 7.6, 7.5, 7.4, and 7.3 s vulnerable to a denial-of-service attack due to uncontrolled recursion in the Integrated Language Environment (ILE) compiler. An authenticated attacker could exploit this vulnerability by compiling specially crafted source code containing a specific combination of statements.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIBM i systems running versions 7.3 through 7.6 contain a denial-of-service vulnerability in the Integrated Language Environment (ILE) compiler. An authenticated attacker with the ability to compile source code can trigger uncontrolled recursion by compiling specially crafted source code containing a specific combination of statements, causing the compiler to consume excessive resources and potentially crash the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.3, <= 7.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check IBM i system versionRun command: DSPSFWRSC (Display Software Resources) or WRKSYSVAL SYSVAL(QSYSDSSR) to confirm the OS version. Verify it falls within 7.3 through 7.6 range.Affected if Version is 7.3, 7.4, 7.5, or 7.6
-
Verify ILE compiler availabilityRun command: GO CMDILE (ILE Commands menu) or DSPQRYF to see if ILE compiler functions are present on the system.Affected if ILE compiler component is installed and available
-
Check user compilation authorityRun command: WRKUSRPRF USRPRF(*ALL) and examine the special authorities, specifically the compiler-related permissions. Also check object authority to ILE compiler programs in QSYS.Affected if User has compile permissions (has *ALLOBJ or specific compiler authorities)
-
Monitor for unusual compilation activityReview job logs using WRKJOB OPTION(*LOG) and check for excessive compilation jobs. Use DSPLOG to search for COMPILER or CRTBND* commands in recent history.Affected if High volume of compilation jobs from any user is observed
-
Check system resource consumptionRun command: WRKACTJOB to review CPU and memory usage. Look for compiler jobs consuming excessive resources or in stuck/waiting states.Affected if Compiler jobs are consuming abnormally high resources or showing recursive behavior
System is affected if running IBM i version 7.3-7.6 AND the ILE compiler is installed AND users with compilation permissions exist on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict compiler permissions to only trusted, authorized users; monitor for unusual compilation activity; apply IBM patches when released. Consider implementing compilation quotas or resource limits for the ILE compiler.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data