CVE-2025-36376
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 Security QRadar EDR 3.12 through 3.12.23 does not invalidate session after a session expiration which could allow an authenticated user to impersonate another user on the system.
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 · high confidenceIBM Security QRadar EDR versions 3.12 through 3.12.23 fails to invalidate user sessions after session expiration, allowing an authenticated attacker to continue using an expired session to impersonate other users on 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>= 3.12.0, < 3.12.24CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Check installed QRadar EDR versionRun 'rpm -q ibm-security-qradar-edr' or access the QRadar EDR management console and navigate to System > About to view the installed versionAffected if The installed version is 3.12.0 through 3.12.23 (versions prior to 3.12.24)
-
Confirm user authentication is enabledVerify that QRadar EDR has user authentication configured and active by checking the admin console under User Management or by reviewing authentication-related configuration files in /opt/qradar/confAffected if User authentication is enabled and users are logging in to the system
-
Review authentication logs for session reuseExamine QRadar EDR authentication logs (typically in /opt/qradar/logs/ or accessible via the console) for entries showing session tokens being used after their expected expiration timeAffected if Logs indicate sessions continuing to work or being reused after the documented session timeout period has elapsed
You are affected if QRadar EDR version 3.12.0 through 3.12.23 is installed with active user authentication, since the session expiration validation flaw allows expired sessions to remain valid.
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 · scoped3.12.24
Apply the vendor patch for CVE-2025-36376 to upgrade QRadar EDR beyond version 3.12.23. Until patched, monitor authentication logs for anomalous session reuse patterns and consider enforcing additional session controls.
3.12.24 or later stable release
- 1. Backup current QRadar EDR configuration and data according to IBM backup procedures
- 2. Verify current installed version of QRadar EDR is between 3.12.0 and 3.12.23
- 3. Download IBM Security QRadar EDR version 3.12.24 or later from IBM Fix Central or authorized distribution channel
- 4. Stop QRadar EDR services following official IBM shutdown procedures
- 5. Install the upgrade to version 3.12.24 or latest available stable release
- 6. Verify the upgrade completed successfully by checking the version number
- 7. Start QRadar EDR services
- 8. Validate that session management is working correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2025-36376 — 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-36376 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