Medium · CVSS 5.3CVE-2025-5988

Aap-gateway: csrf origin checking is disabledCVE-2025-5988

Answer in brief

CVE-2025-5988 records a Medium severity (CVSS 5.3) vulnerability in Aap-gateway: csrf origin checking is disabled. The current sources do not mark it as known exploited. The current feed maps automation-gateway-server (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 4, 2025Updated Nov 5, 2026Source checked Nov 5, 2026First seen by HOL Nov 5, 2026Material review Nov 5, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps automation-gateway-server (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
automation-gateway-servergeneric	>=0 <2.5.20250730	2.5.20250730

Recommended response

Check inventory. Check lockfiles and deployed manifests for automation-gateway-server.
Review the reported fix. Source-reported workaround: Use HTTPS on the platform ingress if possible. Since this is a problem in edge-terminated AAP deployments where requests have TLS terminated right before the platform ingress, enforce trusted origins before requests reach the gateway. A tool such as a Web-application firewall should be able to manage this issue.

Evidence timeline and material changes

Published upstream
Aug 4, 2025
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Nov 5, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.

Package

Affected range

Fixed version

automation-gateway-servergeneric

>=0 <2.5.20250730

2.5.20250730

Recommended response

Check inventory. Check lockfiles and deployed manifests for automation-gateway-server.

Review the reported fix. Source-reported workaround: Use HTTPS on the platform ingress if possible. Since this is a problem in edge-terminated AAP deployments where requests have TLS terminated right before the platform ingress, enforce trusted origins before requests reach the gateway. A tool such as a Web-application firewall should be able to manage this issue.

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.