Is yard 0.9 vulnerable?
RubyGems · 46 releases from 0.9.0 to 0.9.45 · latest yard is 0.9.45 · checked 18 Nov 2026
No known advisories in the last release
yard 0.9.45, the last 0.9 release, has no known advisories. 5 advisories affect earlier 0.9.x releases, so update to 0.9.45.
bundle update --conservative yard # Gemfile: '>= 0.9.45'Is your project on an affected yard?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 0.9.x, affecting earlier releases
YARD static cache reads raw traversal paths before router sanitization
- Affected
- <0.9.44
- Fixed in
- 0.9.44
yard: Possible arbitrary path traversal and file access via yard server
- Affected
- <0.9.42
- Fixed in
- 0.9.42
YARD's default template vulnerable to Cross-site Scripting in generated frames.html
- Affected
- <0.9.36
- Fixed in
- 0.9.36
Path Traversal vulnerability that affects yard
- Affected
- <0.9.20
- Fixed in
- 0.9.20
Arbitrary file read vulnerability in yard server
- Affected
- <0.9.11
- Fixed in
- 0.9.11
Every yard 0.9.x release
Affected: 0.9.0 to 0.9.43. 0.9.44 and later are not affected.
| Version | Known advisories |
|---|---|
| yard 0.9.45 | None |
| yard 0.9.44 | None |
| yard 0.9.43 | CVE-2026-49342 |
| yard 0.9.42 | CVE-2026-49342 |
| yard 0.9.41 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.40 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.39 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.38 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.37 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.36 | CVE-2026-49342, CVE-2026-41493 |
| yard 0.9.35 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.34 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.33 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.32 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.31 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.30 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.29 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.28 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.27 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.26 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.25 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.24 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.23 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.22 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.21 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.20 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285 |
| yard 0.9.19 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.18 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.17 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.16 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.15 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.14 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.13 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.12 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.11 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001 |
| yard 0.9.10 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.9 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.8 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.7 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.6 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.5 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.4 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.3 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.2 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.1 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
| yard 0.9.0 | CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042 |
Which of your client projects are still on yard 0.9?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact yard version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other yard versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.