Security Digest · Vulnerability record
CVE-2023-26153: geokit-rails Command Injection vulnerability
Versions of the package geokit-rails before 2.5.0 are vulnerable to Command Injection due to unsafe deserialisation of YAML within the 'geolocation' cookie.
CVSS 8.3 High EPSS 3.8% · p90
Should you act?
Normal patch cycle
No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 3.8%, percentile 90: FIRST’s model estimates a 3.8% chance of exploitation activity in the next 30 days, higher than 90% of all scored CVEs (elevated). 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
geokit-rails(RubyGems) < 2.5.0, fixed in 2.5.0. Check your lockfile, including transitive dependencies.
What it is
Versions of the package geokit-rails before 2.5.0 are vulnerable to Command Injection due to unsafe deserialisation of YAML within the 'geolocation' cookie. This issue can be exploited remotely via a malicious cookie value. Note: An attacker can use this vulnerability to execute commands on the host system.
From the GitHub advisory
Versions of the package geokit-rails before 2.5.0 are vulnerable to Command Injection due to unsafe deserialisation of YAML within the 'geolocation' cookie. This issue can be exploited remotely via a malicious cookie value.
Note:
An attacker can use this vulnerability to execute commands on the host system.
Weakness type: CWE-78, CWE-77, CWE-502.
Product: geokit-rails (RubyGems) · Assigned by: snyk · Published: 2023-10-06
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| RubyGems | geokit-rails | < 2.5.0 | 2.5.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| n/a | geokit-rails | < 2.5.0 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| snyk | 3.1 | 8.3 High | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L/E:P |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- 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 poc, automatable yes, technical impact partial.
- FIRST EPSS (model of 2026-10-21): 3.85% probability of exploitation activity in the next 30 days; percentile 90.
Timeline
- — CVE record published by snyk
- — GitHub-reviewed advisory GHSA-7xvc-v44j-46fh 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-7xvc-v44j-46fh github.com
- CVE.org record CVE-2023-26153 cve.org
- NVD entry CVE-2023-26153 nvd.nist.gov
Other references from the CVE record and advisory
- security.snyk.io security.snyk.io
- gist.github.com gist.github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com
- github.com github.com