NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
💎
💎 RubyGems
Not in CISA KEV
CRITICAL severity

CVE-2025-27590 — oxidized-web

CRITICALFix: ytti/oxidized-web@a5220a0

CVE-2025-27590 is a critical-severity (CVSS 9) Path Traversal vulnerability in oxidized-web. EPSS puts its 30-day exploitation probability at 27.6% (98th percentile). A fix is available for oxidized-web — see the affected versions and patch details below.

Oxidized Web RANCID migration page allows unauthenticated user to gain control over Linux user account

Also known asGHSA-jx6p-9c26-g373
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-27590.

EPSS Exploitation Probability

via FIRST.org ↗
27.6%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs98th percentile — riskier than 98% of all scored CVEsHighest risk
9.14%16.7%24.3%31.8%13.4%27.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
💎oxidized-web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

In oxidized-web (aka Oxidized Web) before 0.15.0, the RANCID migration page allows an unauthenticated user to gain control over the Linux user account that is running oxidized-web.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
💎RubyGemsoxidized-weball versions0.15.0bundle update oxidized-web --conservative

Affected Products

1 product · 1 configurations
Application
oxidized weboxidized_web_project
< 0.15.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for oxidized-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update oxidized-web to 0.15.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-27590 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

In oxidized-web (aka Oxidized Web) before 0.15.0, the RANCID migration page allows an unauthenticated user to gain control over the Linux user account that is running oxidized-web.
O3 Security · Impact-Aware SCA

Is CVE-2025-27590 in your dependencies?

Find it across RubyGems, including transitive dependencies.

CVE-2025-27590: oxidized-web — Fixed in 0.15.0