CVE-2025-33141 Information disclosure in QRadar
Medium 6.5
Published
Updated
Check this codebase for CVE-2025-33141 and fix it if it is affected.
What it is: CVE-2025-33141 is a medium-severity vulnerability in IBM QRadar, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-33141 in the wild and no public exploit code.
Affected product: IBM QRadar. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-33141/ (Markdown: https://insights.sbomify.com/CVE-2025-33141/index.md)
Authenticated users can access sensitive data from backup files due to incorrect permissions in IBM QRadar SIEM.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-33141?
CVE-2025-33141 is a medium-severity vulnerability in IBM QRadar, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
IBM QRadar 7.5.0 through 7.5.0 UP15 Interim Fix 006 could allow an authenticated user to obtain sensitive information from backup files due to incorrect permissions assignment.
Weakness: CWE-497
Which versions are affected by CVE-2025-33141?
How do I fix CVE-2025-33141?
No fix has been published for CVE-2025-33141 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-33141 being exploited?
There is no known exploitation of CVE-2025-33141 in the wild and no public exploit code.
Sources
Also known as GHSA-jx6h-wqj9-j7ph.