CVE-2026-85008
published 2026-09-04CVE-2026-85008: undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from…
PriorityP430medium5.3CVSS 3.1
AVNACLPRNUINSUCNILAN
EPSS
0.12%
1.6th percentile
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explicit Cache-Control directive is stored and later replayed from cache. Because response headers from a remote origin are untrusted, an origin can answer once with a cacheable status and then have the client's own subsequent state-changing requests to that path served from the stale cache entry without ever reaching the origin, an integrity failure that occurs under the interceptor's default configuration. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.
Affected
51 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| ansible-automation-platform | automation-portal | — | — |
| ansible-automation-platform | bootc-automation-portal-rhel9 | — | — |
| devspaces | code-rhel9 | — | — |
| devspaces | dashboard-rhel9 | — | — |
| devspaces | openvsx-rhel9 | — | — |
| devspaces | pluginregistry-rhel9 | — | — |
| exploit-intelligence | vulnerability-analysis-rhel9 | — | — |
| external-secrets-management | console-plugin-rhel9 | — | — |
| grafana | grafana | — | — |
| nodejs | undici | >= 7.0.0 < 7.29.1 | 7.29.1 |
| nodejs | undici | >= 8.0.0 < 8.10.2 | 8.10.2 |
| nodejs_22 | nodejs | — | — |
| nodejs_24 | nodejs | — | — |
| nodejs_26 | nodejs | — | — |
| odf4 | mcg-core-rhel9 | — | — |
| odf4 | ocs-client-console-rhel9 | — | — |
| odf4 | odf-console-rhel9 | — | — |
| odf4 | odf-multicluster-console-rhel9 | — | — |
| openshift-pipelines | pipelines-console-plugin-pf5-rhel9 | — | — |
| openshift-pipelines | pipelines-console-plugin-rhel9 | — | — |
| openshift4 | ose-monitoring-plugin-rhel9 | — | — |
| rhdh | red-hat-developer-hub-backstage-plugin-lightspeed-backend | — | — |
| rhdh | red-hat-developer-hub-backstage-plugin-orchestrator-backend | — | — |
| rhdh | red-hat-developer-hub-backstage-plugin-orchestrator-backend-module-loki | — | — |
| rhdh | red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator | — | — |
CVSS provenance
nvdv3.15.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
vendor_redhat3.7LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
undici vulnerable to caching and replay of unsafe HTTP method responses
ghsa·2026-09-29
CVE-2026-85008 [LOW] CWE-345 undici vulnerable to caching and replay of unsafe HTTP method responses
undici vulnerable to caching and replay of unsafe HTTP method responses
### Impact
undici's `interceptors.cache()` documents that it caches only safe HTTP methods. However, its internal skip-list is built by subtracting the configured methods from the safe-methods set, so an unsafe method (`POST`, `PUT`, `PATCH`, `DELETE`) never lands in the skip-list and is looked up against the cache store. Combined with the storage gate (`canCacheResponse`) having no method check, a heuristically-cacheable response (for example a `404`) with an explicit `Cache-Control: max-age=...` to an unsafe method is stored and replayed on a subsequent identical request. The application's state-changing request never reaches the origin, and undici serves a fabricated response from the cache instead. This occurs wi
Red Hat
undici: undici: Integrity failure due to caching of unsafe HTTP method responses
vendor_redhat·2026-09-04·CVSS 3.7
CVE-2026-85008 [LOW] CWE-444 undici: undici: Integrity failure due to caching of unsafe HTTP method responses
undici: undici: Integrity failure due to caching of unsafe HTTP method responses
A flaw was found in undici. The cache interceptor incorrectly caches responses to unsafe HTTP methods, such as POST, PUT, or DELETE. A remote attacker can exploit this by providing a cacheable response, leading to subsequent state-changing requests being served from a stale cache entry without reaching the origin. This can result in an integrity failure, where the client's application state is not updated as expected.
Package: exploit-intelligence/vulnerability-analysis-rhel9 (Exploit Intelligence) - Out of support scope
Package: openshift-pipelines/pipelines-console-plugin-pf5-rhel9 (OpenShift Pipelines) - Fix deferred
Package: openshift-pipelines/pipelines-console-plugin-rhel9 (OpenShift Pipelines) - Fix
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-85008 nodejs24: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
bugzilla·2026-09-24·CVSS 5.3
CVE-2026-85008 [MEDIUM] CVE-2026-85008 nodejs24: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
CVE-2026-85008 nodejs24: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explici
Bugzilla
CVE-2026-85008 nodejs20: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
bugzilla·2026-09-24·CVSS 5.3
CVE-2026-85008 [MEDIUM] CVE-2026-85008 nodejs20: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
CVE-2026-85008 nodejs20: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explici
Bugzilla
CVE-2026-85008 nodejs22: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
bugzilla·2026-09-24·CVSS 5.3
CVE-2026-85008 [MEDIUM] CVE-2026-85008 nodejs22: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
CVE-2026-85008 nodejs22: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explici
Bugzilla
CVE-2026-85008 fbthrift: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
bugzilla·2026-09-24·CVSS 5.3
CVE-2026-85008 [MEDIUM] CVE-2026-85008 fbthrift: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
CVE-2026-85008 fbthrift: undici: Integrity failure due to caching of unsafe HTTP method responses [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explici
Bugzilla
CVE-2026-85008 undici: undici: Integrity failure due to caching of unsafe HTTP method responses
bugzilla·2026-09-04·CVSS 5.3
CVE-2026-85008 [MEDIUM] CVE-2026-85008 undici: undici: Integrity failure due to caching of unsafe HTTP method responses
CVE-2026-85008 undici: undici: Integrity failure due to caching of unsafe HTTP method responses
undici's cache interceptor documents that only safe HTTP methods are cached, but its logic to skip caching is built by subtracting the configured methods from the set of safe methods, so an unsafe method such as POST, PUT, or DELETE is never placed in the skip list and instead falls through to the full cache-read path. The response-storage gate also lacked a method check, so a response to an unsafe request that is heuristically cacheable or carries an explicit Cache-Control directive is stored and later replayed from cache. Because response headers from a remote origin are untrusted, an origin can answer once with a cacheable status and then have the client's own subsequent state-changing reque
2026-09-04
Published