Skip to content
Fencer Vulns
high 8.3

CVE-2023-26153 json

geokit-rails Command Injection vulnerability

published 2023-10-06 3 y ago modified 2026-06-17 4 mo ago also GHSA-7xvc-v44j-46fh , EUVD-2023-2692

cvss
8.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.8%
EPSS 3.8% chance of exploitation in 30 days, percentile 90%
public exploits
0
none known

Summary

Versions of the package geokit-rails before 2.5.0 are vulnerable to Command Injection due to unsafe deserialisation of YAML within the 'geo_location' 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.

Patch / fix

  • rubygems geokit-rails 2.5.0
  • n/a geokit-rails 2.5.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

3.85% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • security.snyk.io https://security.snyk.io/vuln/SNYK-RUBY-GEOKITRAILS-5920323 referenced PoC, tagged "exploit" by a source, unverified
  • gist.github.com https://gist.github.com/CalumHutton/b7aa1c2e71c8d4386463ac14f686901d referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L/E:P
CNA 3.1 8.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
rubygems geokit-rails
<2.5.0
2.5.0

Affected products

  • n/a geokit-rails

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
  • CWE-502 Deserialization of Untrusted Data
  • CWE-77 Improper Neutralization of Special Elements used in a Command
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.