CVE-2025-1801
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 flaw was found in the Ansible aap-gateway. Concurrent requests handled by the gateway grpc service can result in concurrency issues due to race condition requests against the proxy. This issue potentially allows a less privileged user to obtain the JWT of a greater privileged user, enabling the server to be jeopardized. A user session or confidential data might be vulnerable.
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 confidenceA race condition vulnerability exists in the Ansible AAP gateway's gRPC service where concurrent requests can cause JWT token confusion. During concurrent request processing, a less privileged user may obtain or intercept a JWT token intended for a more privileged user, enabling privilege escalation and unauthorized access to sensitive data.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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.
-
Confirm Ansible AAP installation and versionRun 'ansible-controller --version' or check the installed RPM package version for the ansible-automation-platform-gateway-service packageAffected if The installed version falls within the affected range and has not been patched for CVE-2025-1801
-
Verify gRPC service is enabledCheck the AAP gateway configuration files (typically in /etc/ansible-automation-platform/gateway/) for gRPC service settings. Look for grpc_enabled or similar configuration flagsAffected if gRPC service is enabled in the gateway configuration
-
Inspect gRPC endpoint exposureReview the gateway service configuration and network settings to determine if gRPC endpoints are exposed. Check for exposed ports (typically 8008 or 8443 for gRPC) in the service manifestAffected if gRPC endpoints are publicly or externally accessible beyond the internal cluster network
-
Review authentication and JWT token handling in logsExamine AAP gateway audit logs for concurrent request patterns, failed authentication attempts, or unexpected JWT token usage. Search for entries showing privilege escalation or token confusion indicatorsAffected if Logs show anomalous JWT token behavior or authentication anomalies during concurrent gRPC request processing
-
Check for concurrent session anomaliesReview active user sessions and authentication logs for instances where a user obtained tokens during periods of concurrent request activity, particularly between privilege levelsAffected if Session records indicate a user accessed resources with a token that was issued during a concurrent request window belonging to a higher-privileged user
A defender is affected if running a vulnerable Ansible AAP version with gRPC service enabled, where concurrent gRPC requests could result in JWT token confusion enabling privilege escalation.
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 dataApply the vendor-provided patch for CVE-2025-1801 to address the race condition in the gateway's gRPC request handling. Additionally, review active user sessions and consider rotating JWT tokens as a precautionary measure.
- Consultation4.0 h
- Implementation16.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-1801 — 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-1801 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