CVE-2023-26153: Versions of the package geokit-rails before 2.5.0 are vulnerable to Command Injection due to unsafe deserialis

Q: How do I fix CVE-2023-26153?

geokit-rails: upgrade to 2.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2023-26153 being exploited?

CVE-2023-26153 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2023-26153 affect?

CVE-2023-26153 affects geokit-rails. Severity is high (CVSS 8.3). 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

Q: How urgent is CVE-2023-26153?

Priority 62/100. High severity; EPSS top 10%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 8.3REMOTEUPGRADE

CVE-2023-26153 is a high-severity flaw (CVSS 8.3) affecting geokit-rails. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
EPSS top 10%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	8.3 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	3.8% (top 10%)
CISA exploited list	No
Weakness	CWE-78, CWE-502
Published	2023-10-06
Last modified	2026-06-17

Publisher (CNA): Snyk · Vendor: geokit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-10-06 05:15 UTCPublished CVE record published
2026-06-17 05:42 UTCUpdated Record last modified

geokit geokit-rails UPGRADE

Affected: < 2.5.0

Fixed in: 2.5.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy geokit-rails || rpm -q geokit-rails || geokit-rails --version

2. UPGRADE to 2.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade geokit-rails

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade geokit-rails

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-26153?

geokit-rails: upgrade to 2.5.0. Exact commands for each OS are on this page.

Is CVE-2023-26153 being exploited?

CVE-2023-26153 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-26153 affect?

CVE-2023-26153 affects geokit-rails. Severity is high (CVSS 8.3). 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

How urgent is CVE-2023-26153?

Priority 62/100. High severity; EPSS top 10%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Ruby on Rails vulnerabilities

References

← Back to latest CVEs