LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40690: Bypass of the secureValidation property

All versions of Apache Santuario - XML Security for Java prior to 2.2.3 and 2.1.7 are vulnerable to an issue where the "secureValidation" property is not passed correctly when creating a KeyInfo from a KeyInfoReference element. This allows an attacker to abuse an XPath Transform to extract any local .xml files in a RetrievalMethod element.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw can make a Java XML security library ignore a safety setting while processing XML signature references. In affected Apache Santuario versions, a crafted XML workflow could expose local .xml files that the application account can read. The main business risk is unintended disclosure of configuration, metadata, or other XML-held sensitive data.

Executive priority

Prioritize remediation for internet-facing or partner-facing Java services that process XML signatures. Treat internal-only usage as lower urgency unless sensitive XML files are present. Because the source bundle lacks active exploitation and CVSS data, urgency should be driven by exposure to untrusted XML and data sensitivity.

Technical view

Apache Santuario XML Security for Java before 2.2.3 and 2.1.7 mishandles secureValidation when building KeyInfo from KeyInfoReference. That gap can allow abuse of an XPath Transform through RetrievalMethod to extract local .xml files. The issue is classified as CWE-200 information exposure; no CVSS score is provided in the bundle.

Likely exposure

Exposure is most likely in Java applications or bundled products using vulnerable Apache Santuario XML Security for Java to process XML signatures. Downstream references mention TomEE, CXF, Debian libxml-security-java, Oracle, and NetApp advisories, so dependency and vendor-product inventory matter.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation appears to require attacker influence over XML security inputs processed by an affected application. Impact is limited in the provided description to local .xml file disclosure, not code execution.

Researcher notes

Key research focus is whether secureValidation is preserved through KeyInfoReference and RetrievalMethod handling in the deployed library path. Avoid assuming all XML parsing is affected; validate actual Santuario usage and whether untrusted XML signature content reaches it.

Mitigation direction

  • Upgrade Apache Santuario XML Security for Java to 2.2.3, 2.1.7, or later.
  • Apply operating system or vendor updates for bundled libxml-security-java packages.
  • Check downstream product advisories for TomEE, CXF, Oracle, NetApp, or other bundled usage.
  • Reduce attacker-controlled XML signature processing where business workflows allow.
  • Follow Apache or vendor guidance if upgrade constraints exist.

Validation and detection

  • Inventory direct and transitive xmlsec or Santuario dependencies in Java applications.
  • Confirm deployed versions are 2.2.3, 2.1.7, later, or vendor-patched.
  • Review products bundling the library, not only application pom or jar names.
  • Identify services that process externally supplied XML signatures or documents.
  • Check vendor security advisories for patched build numbers in packaged products.
Prepared
Confidence
high
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-40690 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
15Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Apache Software FoundationApache SantuarioXML Security for JavaListed
Weakness

CWE details

CWE-200

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs