CVE-2025-33122
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.2, 7.3, 7.4, 7.5, and 7.6 could allow a user to gain elevated privileges due to an unqualified library call in IBM Advanced Job Scheduler for i. A malicious actor could cause user-controlled code to run with administrator privilege.
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 Advanced Job Scheduler for i contains an unqualified library call vulnerability that allows privilege escalation. By exploiting the lack of proper library qualification in the job scheduler, a malicious user can inject user-controlled code that executes with administrator/elevated privileges.
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.2= 7.3= 7.4= 7.5= 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.
-
Verify IBM Advanced Job Scheduler is installedOn IBM i, use the command WRKPRD INSTALLED to list installed products, or run GO LICPGM and select option 10 to work with installed licensed programs. Look for the Advanced Job Scheduler product (typically product ID 5770JS1).Affected if IBM Advanced Job Scheduler is not installed on the system - the vulnerability only applies if this product is present.
-
Confirm the installed IBM i operating system versionRun command DSPSYSVAL QSYSLIBL and review the system version, or use the command WRKSYSACT to display system activity and identify the OS version. Alternatively, run GO CMDDSPF and select option 5 to display system version.Affected if The system runs IBM i version 7.2, 7.3, 7.4, 7.5, or 7.6 - these are the affected versions per the CVE.
-
Identify the IBM Advanced Job Scheduler versionUse the command GO LICPGM, select option 10 to work with installed licensed programs, then option 5 to display installed product information. Locate the Advanced Job Scheduler entry and note its version and release level.Affected if The installed version of IBM Advanced Job Scheduler falls within the vulnerable version range for your IBM i version.
-
Check if the Advanced Job Scheduler service is enabledUse the command WRKSBS to view subsystems. Look for the job scheduler subsystem (commonly QSYS/JS). Or use ENDJS (End Job Scheduler) to check if it can be ended - if it responds, the scheduler is active.Affected if The Advanced Job Scheduler is actively running - the vulnerability requires the scheduler service to be available for exploitation.
-
Review user authorities to Job Scheduler objectsUse the command WRKOBJ *ALL/QSYSJRN and inspect authorities, or run WRKOBJLCK for job scheduler objects. Use DSPOBJAUT for key job scheduler objects to see which users have authority to create or modify jobs.Affected if Non-administrative users have elevated permissions to create, modify, or submit jobs in the scheduler - the privilege escalation requires a malicious user to have job submission access.
The environment is affected if IBM i versions 7.2-7.6 are running with IBM Advanced Job Scheduler installed, enabled, and accessible to users who could inject malicious code through the unqualified library call vulnerability.
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.
dbcve · scopedApply IBM's security patch for this vulnerability when available. In the interim, restrict administrative access to IBM Advanced Job Scheduler, limit job creation/modification permissions to trusted personnel only, and monitor for unauthorized job submissions.
IBM i 7.6 if not already on a supported release, as it is mentioned in the official description as potentially affected but may have the fix integrated
- 1. Locate the IBM security bulletin for CVE-2025-33122 at support.ibm.com or through IBM iaccess security resources
- 2. Identify the specific PTF (Program Temporary Fix) numbers listed for your IBM i version (7.2, 7.3, 7.4, 7.5, or 7.6)
- 3. Download and apply the corresponding PTF to your IBM i system using the GO PTF command or System i Navigator
- 4. After applying the PTF, verify the fix is active by checking PTF status shows 'applied' and then 'loaded'
- 5. Schedule an appropriate maintenance window toIPL (Initial Program Load) the system if required for the PTF to take full effect
- 6. Confirm the unqualified library call in IBM Advanced Job Scheduler for i has been corrected by reviewing any post-fix IBM documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33122 — 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-2025-33122 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