Vulnerability in SAP Approuter (CVE-2026-66776)
Summary
Vulnerability in SAP Approuter (CVE-2026-66776). Confidential information can be exposed externally.
Original description
The description as published by the source.
SAP Approuter does not consistently enforce integrity verification on certain session-related request headers under specific conditions. An attacker with low privileges could send a specially crafted request that bypasses the integrity check and loads another user's session context. Successful exploitation requires the attacker to have previously observed matching session values out-of-band, which makes the attack complex to execute. This could result in a high impact on confidentiality and a low impact on integrity. There is no impact on availability.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-66776 has been found in SAP Approuter.
Confidential information can be exposed externally. CVSS score: 5.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "SAP Approuter CVE-2026-66776" on the vendor's site.
CVE-2026-66776 (SAP Approuter) — CWE-347 / CVSS v3 5.9
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in SAP Approuter.
Check the vendor advisory for the affected versions of SAP Approuter.
Severity: Medium (CVSS 5.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで SAP Approuter を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch cna@sap.com
- web cna@sap.com
- web nvd.nist.gov
- web github.com