dbcve.org
XML External Entity (XXE)Weakness · CWE-611

CVE-2026-46722

MEDIUM · 5.9 CVSS v4.0 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The OOXML parsing of the file indexer does not disable external entity resolution. A crafted xlsx or pptx document placed in an indexed directory can cause local files to be read or outbound HTTP requests to be performed, with the retrieved content being written to the search index.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The file indexer's OOXML parser fails to disable XML external entity (XXE) processing, allowing crafted .xlsx or .pptx files to trigger inbound file reads from the local system or outbound HTTP requests to external servers, with the exfiltrated content subsequently written to the search index.

MitigationDisable external entity resolution in the OOXML XML parser configuration, or process Office documents in a sandboxed/isolated environment before indexing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the file indexer processes OOXML files
    Search configuration files for .xlsx or .pptx file type handlers, or look for OOXML/microsoft-office parser modules. Common locations: indexer config, plugin directories, or registry entries for file type associations.
    Affected if OOXML file processing is enabled and no XXE protection is configured in the XML parser settings
  2. Locate the XML parser configuration used by the OOXML parser
    Inspect the indexer configuration or source code for XML parser instantiation. Look for parser settings files, XML processing libraries (javax.xml.parsers, lxml, etc.), or parser configuration sections.
    Affected if The parser configuration does not explicitly disable external entity resolution (DTD processing, external entity loading, or XInclude support)
  3. Verify XXE protection settings in the XML parser
    Search for parser security settings such as: 'setFeature("http://apache.org/xml/features/disallow-doctype-decl", true)', 'XMLConstants.ACCESS_EXTERNAL_DTD', 'XMLConstants.ACCESS_EXTERNAL_SCHEMA', or similar disable XXE configurations. Check if FEATURE_SECURE_PROCESSING is enabled.
    Affected if XXE protection features are absent, commented out, or set to allow external entities
  4. Check if the indexer writes parsed content to a searchable index
    Verify that the search index stores or indexes the content extracted from Office documents. Look for index storage directories, Solr/Elasticsearch configurations, or database tables holding indexed document content.
    Affected if Parsed content from .xlsx/.pptx files is written to the search index without sanitization of exfiltrated data
  5. Test for XXE vulnerability in a controlled manner
    Create a test .xlsx file with an XXE payload (DOCTYPE with external entity reference to a local file or internal HTTP server). Process it through the indexer and verify if the external resource was accessed or if the entity content appears in search results.
    Affected if The parser successfully resolves external entities and indexes the retrieved content

The environment is affected if the file indexer processes .xlsx or .pptx files using an XML parser that does not explicitly disable external entity resolution, allowing attacker-controlled files to trigger outbound/inbound requests with exfiltrated content indexed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable external entity resolution in the OOXML XML parser configuration, or process Office documents in a sandboxed/isolated environment before indexing.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46722 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46722 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data