How severe is GHSA-mr3q-g2mv-mr4q?

No CVSS score has been assigned to GHSA-mr3q-g2mv-mr4q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mr3q-g2mv-mr4q?

GHSA-mr3q-g2mv-mr4q affects the following packages: sinatra (RubyGems). Ecosystems affected: RubyGems.

How do I fix GHSA-mr3q-g2mv-mr4q?

Update sinatra to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mr3q-g2mv-mr4q is resolved across your whole dependency graph.

How do I detect GHSA-mr3q-g2mv-mr4q in my RubyGems dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sinatra. 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-mr3q-g2mv-mr4q 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-mr3q-g2mv-mr4q?

O3 pinpoints whether GHSA-mr3q-g2mv-mr4q 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-mr3q-g2mv-mr4q actively exploited in the wild?

No public exploit code has been indexed for GHSA-mr3q-g2mv-mr4q 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-mr3q-g2mv-mr4q?

GHSA-mr3q-g2mv-mr4q is classified as CWE-1333 (CWE-1333). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mr3q-g2mv-mr4q published, and has it been updated?

GHSA-mr3q-g2mv-mr4q was published on October 10, 2025 and was last updated on February 4, 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-mr3q-g2mv-mr4q

Fix: sinatra/sinatra#1823

GHSA-mr3q-g2mv-mr4q is a CWE-1333 vulnerability in sinatra. O3 Security confirms whether GHSA-mr3q-g2mv-mr4q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Sinatra is vulnerable to ReDoS through ETag header value generation

Also known asCVE-2025-61921

Published

Oct 10, 2025

Updated

Feb 4, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

💎sinatra

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

Summary

There is a denial of service vulnerability in the If-Match and If-None-Match header parsing component of Sinatra, if the etag method is used when constructing the response and you are using Ruby < 3.2.

Details

Carefully crafted input can cause If-Match and If-None-Match header parsing in Sinatra to take an unexpected amount of time, possibly resulting in a denial of service attack vector. This header is typically involved in generating the ETag header value. Any applications that use the etag method when generating a response are impacted if they are using Ruby below version 3.2.

Resources

https://github.com/sinatra/sinatra/issues/2120 (report)
https://github.com/sinatra/sinatra/pull/2121 (fix)
https://github.com/sinatra/sinatra/pull/1823 (older ReDoS vulnerability)
https://bugs.ruby-lang.org/issues/19104 (fix in Ruby >= 3.2)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`sinatra`	all versions	4.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for sinatra. 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 sinatra to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mr3q-g2mv-mr4q 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-mr3q-g2mv-mr4q 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-mr3q-g2mv-mr4q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary There is a denial of service vulnerability in the `If-Match` and `If-None-Match` header parsing component of Sinatra, if the `etag` method is used when constructing the response and you are using Ruby < 3.2. ### Details Carefully crafted input can cause `If-Match` and `If-None-Match` header parsing in Sinatra to take an unexpected amount of time, possibly resulting in a denial of service attack vector. This header is typically involved in generating the `ETag` header value. Any applications that use the `etag` method when generating a response are impacted if they are using Ruby

O3 Security · Impact-Aware SCA

Is GHSA-mr3q-g2mv-mr4q in your dependencies?

O3 detects GHSA-mr3q-g2mv-mr4q 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