CVE-2026-41493
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedYARD 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceYARD versions prior to 0.9.42 contain a path traversal vulnerability in the yard server component. The vulnerability allows remote attackers to craft malicious HTTP requests that bypass path sanitization, enabling unauthorized access to arbitrary files on the host filesystem where YARD server is running.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.9.42CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed YARD versionRun 'gem list yard' or 'yard --version' to see the currently installed version of the YARD gemAffected if The displayed version is lower than 0.9.42 (e.g., 0.9.40, 0.9.35, etc.)
-
Identify if yard server is configuredLook for a Gemfile, Gemfile.lock, or .gemspec file that includes the yard gem, or check for a 'yard server' command in any startup scripts, cron jobs, or service configurationsAffected if YARD is present in project dependencies AND the yard server is being used or exposed
-
Verify yard server network exposureCheck if yard server is bound to a reachable network interface (0.0.0.0) or exposed via a web server configuration (nginx, Apache, or reverse proxy)Affected if The yard server is accessible from network locations outside localhost
You are affected if YARD version is below 0.9.42 AND the yard server component is actively being used or exposed on your system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.9.42
Upgrade YARD to version 0.9.42 or later. If upgrading is not immediately possible, restrict network access to the yard server and ensure it is not exposed to untrusted networks.
0.9.42
- Check the current installed version of YARD by running: gem list yard
- Upgrade YARD to version 0.9.42 or later by running: gem install yard -v '>= 0.9.42'
- Verify the upgrade was successful by running: gem list yard
- If using Bundler, update the Gemfile to specify: gem 'yard', '>= 0.9.42' and run: bundle update yard
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41493 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data