What is CVE-2025-55193?

CVE-2025-55193 is a medium-severity security vulnerability in activerecord (rubygems), affecting versions >= 8.0, < 8.0.2.1. It is fixed in 8.0.2.1, 7.2.2.2, 7.1.5.2.

Which versions of activerecord are affected by CVE-2025-55193?

activerecord (rubygems) versions >= 8.0, < 8.0.2.1 is affected.

Is there a fix for CVE-2025-55193?

Yes. CVE-2025-55193 is fixed in 8.0.2.1, 7.2.2.2, 7.1.5.2. Upgrade to this version or later.

Is CVE-2025-55193 exploitable, and should I be worried?

Whether CVE-2025-55193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-55193 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-55193 in activerecord

Q: Which versions of activerecord are affected by CVE-2025-55193?

activerecord (rubygems) versions >= 8.0, < 8.0.2.1 is affected.

Q: Is there a fix for CVE-2025-55193?

Yes. CVE-2025-55193 is fixed in 8.0.2.1, 7.2.2.2, 7.1.5.2. Upgrade to this version or later.

Q: Is CVE-2025-55193 exploitable, and should I be worried?

Whether CVE-2025-55193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-55193 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-55193?

Upgrade: activerecord to 8.0.2.1 or later, activerecord to 7.2.2.2 or later, activerecord to 7.1.5.2 or later.

Summary

Active Record logging vulnerable to ANSI escape injection

This vulnerability has been assigned the CVE identifier CVE-2025-55193

Releases

The fixed releases are available at the normal locations.

Credits

Thanks to lio346 from Unit 515 of OPSWAT for reporting this vulnerability

Impact

The ID passed to find or similar methods may be logged without escaping. If this is directly to the terminal it may include unescaped ANSI sequences.

Affected versions

activerecord (>= 8.0, < 8.0.2.1) activerecord (>= 7.2, < 7.2.2.2) activerecord (>= 0, < 7.1.5.2)

Security releases

activerecord → 8.0.2.1 (rubygems) activerecord → 7.2.2.2 (rubygems) activerecord → 7.1.5.2 (rubygems)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

activerecord to 8.0.2.1 or later; activerecord to 7.2.2.2 or later; activerecord to 7.1.5.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-55193? CVE-2025-55193 is a medium-severity security vulnerability in activerecord (rubygems), affecting versions >= 8.0, < 8.0.2.1. It is fixed in 8.0.2.1, 7.2.2.2, 7.1.5.2.
Which versions of activerecord are affected by CVE-2025-55193? activerecord (rubygems) versions >= 8.0, < 8.0.2.1 is affected.
Is there a fix for CVE-2025-55193? Yes. CVE-2025-55193 is fixed in 8.0.2.1, 7.2.2.2, 7.1.5.2. Upgrade to this version or later.
Is CVE-2025-55193 exploitable, and should I be worried? Whether CVE-2025-55193 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-55193 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-55193?
- Upgrade activerecord to 8.0.2.1 or later
- Upgrade activerecord to 7.2.2.2 or later
- Upgrade activerecord to 7.1.5.2 or later

Other vulnerabilities in activerecord

CVE-IDSeverityPackage summary

CVE-2022-44566Highactiverecord: Denial of Service Vulnerability in ActiveRecord's PostgreSQL adapter CVE-2023-22794Highactiverecord: SQL Injection Vulnerability via ActiveRecord comments CVE-2022-32224Criticalactiverecord: Active Record RCE bug with Serialized Columns CVE-2013-3221Criticalactiverecord: Active Record component in Ruby on Rails has a data-type injection vulnerability CVE-2021-22880Highactiverecord: Active Record subject to Regular Expression Denial-of-Service (ReDoS)