How severe is GHSA-73rx-3f9r-x949?

GHSA-73rx-3f9r-x949 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-73rx-3f9r-x949?

GHSA-73rx-3f9r-x949 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix GHSA-73rx-3f9r-x949?

Update org.apache.tomcat:tomcat to 9.0.0.M22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73rx-3f9r-x949 is resolved across your whole dependency graph.

How do I detect GHSA-73rx-3f9r-x949 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-73rx-3f9r-x949 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.

Is GHSA-73rx-3f9r-x949 actively exploited in the wild?

No public exploit code has been indexed for GHSA-73rx-3f9r-x949 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 is the EPSS score for GHSA-73rx-3f9r-x949?

GHSA-73rx-3f9r-x949 has an EPSS (Exploit Prediction Scoring System) score of 8.0%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-73rx-3f9r-x949?

GHSA-73rx-3f9r-x949 is classified as CWE-345 (CWE-345). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-73rx-3f9r-x949 published, and has it been updated?

GHSA-73rx-3f9r-x949 was published on May 14, 2022 and was last updated on March 11, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Insufficient Verification of Data Authenticity in Apache TomcatGHSA-73rx-3f9r-x949

MEDIUMFix: apache/tomcat@52382eb

GHSA-73rx-3f9r-x949 is a medium-severity (CVSS 4.3) CWE-345 vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Also known asCVE-2017-7674

Published

May 14, 2022

Updated

Mar 11, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

8.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

The CORS Filter in Apache Tomcat 9.0.0.M1 to 9.0.0.M21, 8.5.0 to 8.5.15, 8.0.0.RC1 to 8.0.44 and 7.0.41 to 7.0.78 did not add an HTTP Vary header indicating that the response varies depending on Origin. This permitted client and server side cache poisoning in some circumstances.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 9.0.0.M1&&< 9.0.0.M22	9.0.0.M22`org.apache.tomcat:tomcat:9.0.0.M22`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.5.0&&< 8.5.16	8.5.16`org.apache.tomcat:tomcat:8.5.16`
☕Maven	`org.apache.tomcat:tomcat`	≥ 8.0.0.RC1&&< 8.0.45	8.0.45`org.apache.tomcat:tomcat:8.0.45`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.41&&< 7.0.79	7.0.79`org.apache.tomcat:tomcat:7.0.79`

Affected Products

1 product · 123 configurations

Application

tomcatapache

100 versions

7.0.417.0.427.0.437.0.447.0.457.0.467.0.477.0.487.0.497.0.507.0.527.0.53

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 9.0.0.M22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73rx-3f9r-x949 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 7	`tomcat-0:7.0.76-3.el7_4`	RHSA-2017:3081
Red Hat JBoss Web Server 3.1	see advisory	RHSA-2017:1802
Red Hat JBoss Web Server 3 for RHEL 6	`log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el6`	RHSA-2017:1801

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-73rx-3f9r-x949 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works