Path Traversal in yard (CVE-2026-41493)
Summary
Path traversal in yard (CVE-2026-41493). Confidential information can be exposed externally. Mitigation: upgrade to 0.9.42 or later.
Original description
The description as published by the source.
YARD is a Ruby Documentation tool. Prior to version 0.9.42, a path traversal vulnerability was discovered in YARD when using yard server to serve documentation. This bug would allow unsanitized HTTP requests to access arbitrary files on the machine of a yard server host under certain conditions. This issue has been patched in version 0.9.42.
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-41493 has been found in yard.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade yard to 0.9.42 or later.
If unsure, ask your IT team or search "yard CVE-2026-41493" on the vendor's site.
CVE-2026-41493 (yard) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.9.42 — apply immediately
Workaround: For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level.
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 yard.
Check the vendor advisory for the affected versions of yard.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 0.9.42.
Workaround: For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'yard' . 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 'yard' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
yardを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level.パッチが適用されるまでの応急処置として、For users who cannot upgrade, it is possible to perform path sanitization of HTTP requests at your webserver level. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade yard to 0.9.42ステージング環境で 0.9.42 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-41493 yard
- Ubuntu UBUNTU-CVE-2026-41493 yard Fixed in: 0.8.7.6+git20160220-3ubuntu0.1~esm2
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com