How severe is GHSA-76r7-hhxj-r776?

No CVSS score has been assigned to GHSA-76r7-hhxj-r776 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-76r7-hhxj-r776?

GHSA-76r7-hhxj-r776 affects the following packages: activerecord (RubyGems), activerecord (RubyGems), activerecord (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-76r7-hhxj-r776?

Update activerecord to 8.0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-76r7-hhxj-r776 is resolved across your whole dependency graph.

How do I detect GHSA-76r7-hhxj-r776 in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-76r7-hhxj-r776 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-76r7-hhxj-r776?

O3 pinpoints whether GHSA-76r7-hhxj-r776 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-76r7-hhxj-r776 actively exploited in the wild?

No public exploit code has been indexed for GHSA-76r7-hhxj-r776 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-76r7-hhxj-r776?

GHSA-76r7-hhxj-r776 is classified as CWE-150 (CWE-150). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-76r7-hhxj-r776 published, and has it been updated?

GHSA-76r7-hhxj-r776 was published on August 13, 2025 and was last updated on February 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

GHSA-76r7-hhxj-r776

Fix: rails/rails@3beef20

GHSA-76r7-hhxj-r776 is a CWE-150 vulnerability in activerecord. O3 Security confirms whether GHSA-76r7-hhxj-r776 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Active Record logging vulnerable to ANSI escape injection

Also known asCVE-2025-55193

Published

Aug 13, 2025

Updated

Feb 5, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Feb 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

💎activerecord💎activerecord💎activerecord

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects RubyGems packages — download data is not available via public APIs for these ecosystems.

Description

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

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.

Releases

The fixed releases are available at the normal locations.

Credits

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

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`activerecord`	≥ 8.0&&< 8.0.2.1	8.0.2.1
💎RubyGems	`activerecord`	≥ 7.2&&< 7.2.2.2	7.2.2.2
💎RubyGems	`activerecord`	all versions	7.1.5.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for activerecord. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update activerecord to 8.0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-76r7-hhxj-r776 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-76r7-hhxj-r776 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-76r7-hhxj-r776. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This vulnerability has been assigned the CVE identifier CVE-2025-55193 ### 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. ### Releases The fixed releases are available at the normal locations. ### Credits Thanks to [lio346](https://hackerone.com/lio346) from Unit 515 of OPSWAT for reporting this vulnerability

O3 Security · Impact-Aware SCA

Is GHSA-76r7-hhxj-r776 in your dependencies?

O3 detects GHSA-76r7-hhxj-r776 across RubyGems dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works