Skip to main content
Mallory
CriticalVulnerability

CVE-2016-4464: SAML AudienceRestriction validation bypass in Apache CXF Fediz plugins

Published Sep 21, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3
EPSS6.5%94th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2016-4464CWE-287

Apache CXF Fediz application plugins (including fediz-spring and fediz-spring2) in versions 1.2.x before 1.2.3 and 1.3.x before 1.3.1 fail to match/validate SAML AudienceRestriction values against the configured audience URIs. As a result, an attacker can present a crafted SAML token that carries a trusted signature but contains AudienceRestriction values that should not be accepted by the relying party, enabling bypass of intended audience-based restrictions.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Remote attackers can bypass intended SAML AudienceRestriction-based access controls/restrictions by supplying a crafted, validly signed SAML token, potentially enabling unauthorized access and other unspecified downstream impacts depending on the protected application’s authorization model.

Mitigation

If you can’t patch tonight, do this now.

No specific workaround is described beyond upgrading. As compensating controls prior to upgrade, restrict SAML token acceptance to trusted identity providers and enforce stricter SAML validation at an upstream gateway/IdP layer where feasible.

Remediation

Patch, then assume compromise.

Upgrade Apache CXF Fediz to a fixed release: 1.2.3+ for the 1.2.x line, or 1.3.1+ for the 1.3.x line.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.

View more in app →
Every candidate exploit was rejected by Mallory's analysis.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationCxf Fedizapplication
FAQ

Frequently asked questions

Is CVE-2016-4464 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2016-4464 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-4464?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2016-4464.
Is there a patch for CVE-2016-4464?
Upgrade Apache CXF Fediz to a fixed release: 1.2.3+ for the 1.2.x line, or 1.3.1+ for the 1.3.x line.
What products are affected by CVE-2016-4464?
Apache Software Foundation Cxf Fediz.
How severe is CVE-2016-4464?
CVE-2016-4464 has a CVSS v3 score of 9.8 (Critical) and an EPSS score of 6.5% (94th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.