# The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials' for all origins

Advisory record · `GHSA-r4x2-3cq5-hqvp`

- **Identifiers:** `GHSA-r4x2-3cq5-hqvp` · `CVE-2018-8014`
- **State:** Confirmed
- **Severity:** CVSS 9.8 Critical
- **Critical:** Yes: CVSS 9+, CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-1188](https://cwe.mitre.org/data/definitions/1188.html)
- **Tags:** [CWE-1188](https://agentprime.io/advisories/tag/cwe-1188.md)
- **Published:** 17 Oct 2018
- **Updated:** 12 Mar 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 17 Oct 2018, 16:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 9.8: 9.0 or more.
- CVSS score 9.8 (7.0 or more) and EPSS 0.21 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `org.apache.tomcat.embed:tomcat-embed-core` (Maven): affected `>=9.0.0.M1, <9.0.9 || >=8.5.0, <8.5.32 || >=8.0.0RC1, <8.0.53 || >=7.0.41, <7.0.88`; fixed in `9.0.9`, `8.5.32`, `8.0.53`, `7.0.88`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Apache Tomcat (org.apache.tomcat.embed:tomcat-embed-core) versions 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, and 7.0.41 to 7.0.88 have insecure default settings in the CORS filter, which enable supportsCredentials for all origins. The source says most users are not affected because the filter is expected to be configured for their environment rather than used with defaults. Upgrade to 9.0.9, 8.5.32, 8.0.53, or 7.0.88, or configure the CORS filter explicitly instead of relying on its defaults.

Written 8 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 9.8 Critical, CVSS 3.0: `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.21, the 97th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-r4x2-3cq5-hqvp)

## Sources

- [GitHub Advisory Database: GHSA-r4x2-3cq5-hqvp](https://github.com/advisories/GHSA-r4x2-3cq5-hqvp)
- [OSV: GHSA-r4x2-3cq5-hqvp](https://osv.dev/vulnerability/GHSA-r4x2-3cq5-hqvp)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-8014>
- <https://github.com/apache/tomcat80/commit/2c9d8433bd3247a2856d4b2555447108758e813e>
- <https://github.com/apache/tomcat/commit/d83a76732e6804739b81d8b2056365307637b42d>
- <https://github.com/apache/tomcat/commit/5877390a9605f56d9bd6859a54ccbfb16374a78b>
- <https://github.com/apache/tomcat/commit/60f596a21fd6041335a3a1a4015d4512439cecb5>
- <https://lists.apache.org/thread.html/r9136ff5b13e4f1941360b5a309efee2c114a14855578c3a2cbe5d19c%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r6ccee4e849bc77df0840c7f853f6bd09d426f6741247da2b7429d5d9@%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r6ccee4e849bc77df0840c7f853f6bd09d426f6741247da2b7429d5d9%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0@%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r48c1444845fe15a823e1374674bfc297d5008a5453788099ea14caf0%40%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d@%3Cdev.tomcat.apache.org%3E>
- <https://lists.apache.org/thread.html/r3bbb800a816d0a51eccc5a228c58736960a9fffafa581a225834d97d%40%3Cdev.tomcat.apache.org%3E>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-r4x2-3cq5-hqvp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-r4x2-3cq5-hqvp/>. Everything for agents: <https://agentprime.io/llms.txt>.
