# CVE-2018-8014: The defaults settings for the CORS filter provided in Apache Tomcat are insecure and enable 'supportsCredentials' for all origins > Insecure default CORS settings in Apache Tomcat allow credentials from all origins, potentially bypassing security controls if not explicitly configured. - **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 16 May 2018 - **Updated:** 15 Oct 2026 - **Also known as:** CLSA-2026-1777884162, GHSA-r4x2-3cq5-hqvp, UBUNTU-CVE-2018-8014 ## What is CVE-2018-8014? CVE-2018-8014 is a critical vulnerability in Apache Tomcat, published on 16 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description The defaults settings for the CORS filter provided in Apache Tomcat 9.0.0.M1 to 9.0.8, 8.5.0 to 8.5.31, 8.0.0.RC1 to 8.0.52, 7.0.41 to 7.0.88 are insecure and enable 'supportsCredentials' for all origins. It is expected that users of the CORS filter will have configured it appropriately for their environment rather than using it in the default configuration. Therefore, it is expected that most users will not be impacted by this issue. Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default) ## Which versions are affected by CVE-2018-8014? 8 open source packages ship an affected version, including org.apache.tomcat.embed:tomcat-embed-core. It affects 8 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.41 | 7.0.88 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 7.0.41 | 7.0.88 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0RC1 | 8.0.53 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.0.0RC1 | 8.0.53 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.32 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 8.5.0 | 8.5.32 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.9 | | `org.apache.tomcat.embed:tomcat-embed-core` | Maven | From 9.0.0.M1 | 9.0.9 | Products: Apache Tomcat, Canonical Ubuntu Linux, Debian Debian Linux, Netapp Oncommand Insight, Netapp Oncommand Unified Manager, Netapp Oncommand Workflow Automation, Netapp Snapcenter Server, Netapp Storage Automation Store. ## How do I fix CVE-2018-8014? Upgrade org.apache.tomcat.embed:tomcat-embed-core to a fixed version for your release line: 7.0.88, 8.0.53, 8.5.32 or 9.0.9. ## Is CVE-2018-8014 being exploited? There is no known exploitation of CVE-2018-8014 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-8014 and fix it if it is affected. What it is: CVE-2018-8014 is a critical vulnerability in Apache Tomcat, published on 16 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2018-8014 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.41; fixed in 7.0.88 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 7.0.41; fixed in 7.0.88 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0RC1; fixed in 8.0.53 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.0.0RC1; fixed in 8.0.53 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.32 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 8.5.0; fixed in 8.5.32 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.9 - org.apache.tomcat.embed:tomcat-embed-core (Maven): affected from 9.0.0.M1; fixed in 9.0.9 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-8014/ (Markdown: https://insights.sbomify.com/CVE-2018-8014/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8014 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8014 - OSV: https://osv.dev/vulnerability/CVE-2018-8014 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-8014/ Summaries are generated and may contain mistakes; the official description above is the record.