CVE-2026-11807
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 missing authorization vulnerability was found in the Event-Driven Ansible (EDA) websocket API. The /api/eda/ws/ansible-rulebook endpoint does not verify user permissions when processing Worker messages. Any authenticated user can send a forged message with an arbitrary activation_id to receive plaintext credentials associated with that activation, including OAuth tokens, vault passwords, and SSH keys.
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 confidenceThe Event-Driven Ansible websocket API endpoint /api/eda/ws/ansible-rulebook fails to verify user permissions when processing Worker messages. This allows any authenticated user to forge messages containing an arbitrary activation_id and receive plaintext credentials (OAuth tokens, vault passwords, SSH keys) associated with that activation, regardless of ownership.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
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 EDA server is runningCheck if the Event-Driven Ansible service is running and the websocket endpoint /api/eda/ws/ansible-rulebook is accessible. Look for the EDA server process or check network listeners on typical EDA ports (8000, 8080, or configured port).Affected if EDA server is running and the websocket API endpoint is exposed to users or network segments that include untrusted users.
-
Verify websocket endpoint respondsAttempt a websocket connection to /api/eda/ws/ansible-rulebook using a websocket client. The endpoint should accept connections if EDA is running.Affected if The websocket endpoint accepts connections without immediate authorization failures.
-
Check authentication requirements on websocketExamine if the websocket endpoint enforces authentication. Look at EDA server configuration files (eda-server.yml, settings.py) or test with an unauthenticated websocket connection attempt.Affected if The websocket endpoint can be accessed with any valid authentication token rather than requiring activation-specific authorization.
-
Test cross-activation credential accessUsing an authenticated session for one activation, attempt to send a Worker message to the websocket with an activation_id different from the one the user is authorized for. Check if the server returns credentials (OAuth tokens, vault passwords, SSH keys) for that foreign activation.Affected if The server returns credential data for activations the authenticated user is not authorized to access.
-
Review EDA authorization configurationInspect the EDA server configuration and code for permission verification on the websocket endpoint. Look for checks that validate user authorization to a specific activation_id before returning credential data.Affected if No authorization check exists between the received activation_id in websocket messages and the authenticated user's permissions.
A user is affected if they can retrieve credentials for any activation by sending a forged message with an arbitrary activation_id through the websocket API, regardless of whether they are authorized for that activation.
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 proper authorization checks in the websocket endpoint to verify that the authenticated user has permission to access credentials for the requested activation_id before returning any sensitive data.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11807 — 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-2026-11807 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