Security Digest · Vulnerability record
CVE-2025-27590: Oxidized Web RANCID migration page allows unauthenticated user to gain control over Linux user account
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.
CVSS 9.0 Critical EPSS 27.6% · p98
Should you act?
High exploit likelihood
EPSS ranks it in the top 5% of all CVEs for likely exploitation in the next 30 days. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 27.6%, percentile 98: FIRST’s model estimates a 27.6% chance of exploitation activity in the next 30 days, higher than 98% of all scored CVEs (very high). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes
oxidized-web(RubyGems) < 0.15.0, fixed in 0.15.0. Check your lockfile, including transitive dependencies.
What it is
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.
From the GitHub advisory
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.
Weakness type: CWE-22.
Product: oxidized-web (RubyGems) · Assigned by: mitre · Published: 2025-03-03
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| RubyGems | oxidized-web | < 0.15.0 | 0.15.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| Oxidized Web project | Oxidized Web | < 0.15.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| mitre | 3.1 | 9 Critical | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 9.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: high (needs special conditions)
- Privileges required: none (no login)
- User interaction: none
- Scope: changed (can affect other components)
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 27.57% probability of exploitation activity in the next 30 days; percentile 98.
Timeline
- — CVE record published by mitre
- — GitHub-reviewed advisory GHSA-jx6p-9c26-g373 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-jx6p-9c26-g373 github.com
- CVE.org record CVE-2025-27590 cve.org
- NVD entry CVE-2025-27590 nvd.nist.gov
Other references from the CVE record and advisory
- github.com github.com
- github.com github.com