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.

Update within 0.9:bundle update --conservative yard # Gemfile: '>= 0.9.45'

Is your project on an affected yard?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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

  • MediumCVE-2026-49342GHSA-pxcc-8665-phx826 Jun 2026

    YARD static cache reads raw traversal paths before router sanitization

    Affected
    <0.9.44
    Fixed in
    0.9.44
  • MediumCVE-2026-41493GHSA-3jfp-46x4-xgfj17 Apr 2026

    yard: Possible arbitrary path traversal and file access via yard server

    Affected
    <0.9.42
    Fixed in
    0.9.42
  • MediumCVE-2024-27285GHSA-8mq4-9jjh-9xrc28 Feb 2024

    YARD's default template vulnerable to Cross-site Scripting in generated frames.html

    Affected
    <0.9.36
    Fixed in
    0.9.36
  • HighCVE-2019-1020001GHSA-xfhh-rx56-rxcr2 Jul 2019

    Path Traversal vulnerability that affects yard

    Affected
    <0.9.20
    Fixed in
    0.9.20
  • HighCVE-2017-17042GHSA-gj4p-3wh3-2rmf21 Dec 2017

    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.

VersionKnown advisories
yard 0.9.45None
yard 0.9.44None
yard 0.9.43CVE-2026-49342
yard 0.9.42CVE-2026-49342
yard 0.9.41CVE-2026-49342, CVE-2026-41493
yard 0.9.40CVE-2026-49342, CVE-2026-41493
yard 0.9.39CVE-2026-49342, CVE-2026-41493
yard 0.9.38CVE-2026-49342, CVE-2026-41493
yard 0.9.37CVE-2026-49342, CVE-2026-41493
yard 0.9.36CVE-2026-49342, CVE-2026-41493
yard 0.9.35CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.34CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.33CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.32CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.31CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.30CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.29CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.28CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.27CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.26CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.25CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.24CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.23CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.22CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.21CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.20CVE-2026-49342, CVE-2026-41493, CVE-2024-27285
yard 0.9.19CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.18CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.17CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.16CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.15CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.14CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.13CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.12CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.11CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001
yard 0.9.10CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.9CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.8CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.7CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.6CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.5CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.4CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.3CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.2CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.1CVE-2026-49342, CVE-2026-41493, CVE-2024-27285, CVE-2019-1020001, CVE-2017-17042
yard 0.9.0CVE-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.