dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-5988

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A flaw was found in the Ansible aap-gateway. Cross-site request forgery (CSRF) origin checking is not done on requests from the gateway to external components, such as the controller, hub, and eda.

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 confidence

The Ansible AAP gateway fails to perform CSRF origin validation on requests it forwards to external components (controller, hub, and eda). This allows attackers to potentially trick authenticated users into unknowingly triggering operations on those components through the gateway, as the gateway doesn't verify the request origin before forwarding.

MitigationImplement and enforce CSRF origin checking on all requests from the gateway to external components, ensuring proper origin header validation and CSRF token enforcement for cross-component communication.

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Ansible AAP gateway installation
    Check if the system is running Ansible Automation Platform (AAP) with the gateway component installed. Look for the 'gateway' service or component in the AAP installation. Common indicators: service named 'gateway', configuration files in /etc/ansible/automation-platform/gateway/ or similar AAP paths, or check the AAP controller API endpoint /api/gateway/
    Affected if The system is running Ansible AAP with the gateway component and forwards requests to external controller, hub, or eda components
  2. Verify gateway forwards to external components
    Check the AAP gateway configuration for upstream or proxy settings pointing to external controller, hub, or EDA components. Look for settings like 'CONTROLLER_HOST', 'HUB_HOST', 'EDA_HOST' in gateway settings, or proxy/ upstream configurations that route traffic to separate controller/hub/eda installations
    Affected if Gateway is configured to proxy/forward requests to separate external components (controller, hub, or eda) rather than running them locally or having those components handle origin validation themselves
  3. Check for CSRF origin validation on gateway
    Inspect the gateway configuration or code for CSRF origin validation settings. Look for settings related to 'CSRF_ORIGIN_CHECK', 'origin_validation', 'ALLOWED_HOSTS', or similar security headers validation in the gateway configuration. Check if the gateway validates Origin or Referer headers before forwarding requests
    Affected if The gateway is missing or has disabled CSRF origin/header validation - no explicit origin checking configured before forwarding requests to external components
  4. Identify exposed gateway endpoints
    Review the gateway's exposed endpoints and routes, particularly those that forward to external components (controller, hub, eda). Check the gateway routing configuration to identify which paths trigger proxy forwarding to those components
    Affected if Gateway exposes endpoints that forward to external components without validating the request origin first

You are affected if you run Ansible AAP with a gateway component that forwards requests to external controller, hub, or eda components without CSRF origin validation enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement and enforce CSRF origin checking on all requests from the gateway to external components, ensuring proper origin header validation and CSRF token enforcement for cross-component communication.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5988 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5988 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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