CVE-2025-9036
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 · uneditedA security issue in the runtime event system allows unauthenticated connections to receive a reusable API token. This token is broadcasted over a WebSocket and can be intercepted by any local client listening on the connection.
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 confidenceThe runtime event system's WebSocket endpoint broadcasts reusable API tokens to unauthenticated connecting clients. Any local client able to listen on the connection can intercept these tokens, allowing unauthorized access to the system using the intercepted credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- P
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 if the runtime event system's WebSocket endpoint is enabledReview application configuration files, runtime settings, or service documentation to determine if the WebSocket endpoint for the event system is exposed or activatedAffected if The WebSocket endpoint is enabled and listening for connections
-
Verify if WebSocket clients receive tokens before authenticationCapture or inspect a WebSocket handshake and initial message exchange between a client and the runtime event system; observe whether tokens are transmitted prior to or without authentication validationAffected if API tokens are sent to connecting clients before or without successful authentication
-
Determine if the transmitted tokens are reusableCapture multiple WebSocket connection attempts from a client; attempt to reuse a token captured from a previous session to access protected resourcesAffected if The same token can be used across multiple sessions or connections without expiration
-
Check if the WebSocket channel lacks encryptionInspect the WebSocket connection URL scheme (ws:// versus wss://) and verify whether TLS/SSL encryption is configured for the event system WebSocket endpointAffected if The WebSocket connection uses an unencrypted protocol (ws://) allowing local network observers to intercept traffic
A user is affected if the runtime event system's WebSocket endpoint is enabled, transmits reusable API tokens to unauthenticated clients, and the channel is unencrypted, enabling local interceptors to capture and reuse credentials for unauthorized access.
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 dataImplement authentication handshake before token transmission over WebSocket, use short-lived or one-time tokens, and encrypt the WebSocket channel to prevent token interception by unauthorized local listeners.
- Consultation4.0 h
- Implementation12.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 $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9036 — 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-9036 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