CVE-2025-36377
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 · moderate confidenceIBM Security QRadar EDR versions 3.12 through 3.12.23 fail to properly invalidate user sessions after session expiration. This session management flaw allows an authenticated attacker who possesses a session token to continue using that token beyond its valid lifetime, potentially enabling impersonation of 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.
-
Identify installed QRadar EDR versionRun the product's version command or check the installation manifest/config file to retrieve the exact version number of IBM Security QRadar EDRAffected if The installed version falls within 3.12.0 through 3.12.23 (any version >= 3.12.0 but < 3.12.24)
-
Confirm session management is in useVerify that user authentication and session handling features are enabled on the QRadar EDR deploymentAffected if User sessions are being created and managed by the system (the vulnerability only applies to deployments with active user sessions)
-
Examine session token handlingReview session configuration files or logs to determine whether the system validates session expiration timestamps on incoming requestsAffected if The system accepts and honors session tokens without rejecting those that have passed their expiration time, indicating improper invalidation is occurring
You are affected if your QRadar EDR version is 3.12.0 through 3.12.23 and the system handles user sessions, since expired session tokens remain valid in these versions.
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 (version 3.12.24 or later) from IBM to remediate the session invalidation issue. Until patched, monitor session logs for anomalous reuse of expired session tokens.
3.12.24 or later
- 1. Identify the current QRadar EDR version by checking the system console or using the qappman command line tool
- 2. Review the IBM QRadar EDR 3.12.24 release notes for any special upgrade instructions or prerequisites
- 3. Create a full backup of the current QRadar EDR configuration and ensure you have a rollback plan
- 4. Schedule a maintenance window as the upgrade may require system downtime
- 5. Download and apply QRadar EDR version 3.12.24 or later from IBM Fix Central or your authorized IBM distribution channel
- 6. After upgrade, verify the installation was successful by checking the version number
- 7. Test session expiration behavior to confirm sessions are properly invalidated after the configured timeout period
- 8. Monitor system logs for any unusual session-related activity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36377 — 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-36377 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