Path Traversal in routinator (CVE-2026-49233)
Summary
Path traversal in routinator (CVE-2026-49233). Confidential information can be exposed externally. Mitigation: upgrade to 0.15.2 or later.
Original description
The description as published by the source.
Routinator does not properly check the module component of rsync URIs, which are used to create the file system paths for the Routinator cache. This allows for path traversal by having a module name containing .., potentially providing an attacker access to the entire Routinator rsync cache.
Source: GitHub Security Advisories (Global) 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-49233 has been found in routinator.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade routinator to 0.15.2 or later.
If unsure, ask your IT team or search "routinator CVE-2026-49233" on the vendor's site.
CVE-2026-49233 (routinator) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.15.2 — 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.
Path traversal (CWE-22) exists in routinator.
Check the vendor advisory for the affected versions of routinator.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.15.2.
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 'routinator' . 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 'routinator' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
routinatorを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade routinator to 0.15.2ステージング環境で 0.15.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory nlnetlabs.nl
- package github.com
- web github.com
- web github.com