Open Redirect in @sap/approuter (CVE-2026-58230)
Summary
Vulnerability in @sap/approuter (CVE-2026-58230). Confidential information can be exposed externally. Mitigation: upgrade to 23.0.0 or later.
Original description
The description as published by the source.
SAP Approuter does not sufficiently validate certain token content under specific configurations. An unauthenticated attacker could send a specially crafted token to cause sensitive credential material to be sent to an attacker-controlled destination. The attack complexity is high due to non-default preconditions required in the target environment. This results in a high impact on confidentiality and a low impact on integrity and 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-58230 has been found in @sap/approuter.
Confidential information can be exposed externally. CVSS score: 7.0/10.
What to do: upgrade @sap/approuter to 23.0.0 or later.
If unsure, ask your IT team or search "@sap/approuter CVE-2026-58230" on the vendor's site.
CVE-2026-58230 (@sap/approuter) — CWE-601 / CVSS v3 7.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 23.0.0 — apply immediately
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-601) exists in @sap/approuter.
Check the vendor advisory for the affected versions of @sap/approuter.
Severity: High (CVSS 7.0/10). Confidential information can be exposed externally.
Update to 23.0.0.
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. Run grep -r '@sap/approuter' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@sap/approuter' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@sap/approuterを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @sap/approuter to 23.0.0ステージング環境で 23.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- web me.sap.com
- web url.sap
- web github.com