CVE-2026-6501
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 · uneditedImproper restriction of XML external entity reference vulnerability in ILM Informatique jOpenDocument allows Data Serialization External Entities Blowup. This issue affects jOpenDocument: 1.5.
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 · moderate confidenceThis is an XML External Entity (XXE) injection vulnerability in jOpenDocument version 1.5, a Java library for creating and reading OpenDocument files. The vulnerable XML parser improperly processes external entity references, allowing attackers to cause denial-of-service (blowup) or potentially read local files via crafted malicious ODF documents.
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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/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 checksWork through these to decide whether this CVE applies to you.
-
Locate jOpenDocument library in your environmentSearch for jOpenDocument JAR files in your project dependencies (Maven pom.xml, Gradle build.gradle, or JARs in lib/ folder) or check the application classpath for the jOpenDocument class (org.jopendocument.*)Affected if jOpenDocument library is found in your dependencies or classpath
-
Determine the installed jOpenDocument versionCheck the version in your dependency management (Maven: mvn dependency:tree, Gradle: gradle dependencies) or inspect the JAR file manifest/META-INF/MANIFEST.MFAffected if The version is 1.5 (exactly) or falls within the 1.5.x branch
-
Confirm ODF document processing is in useInspect your application code for usage of jOpenDocument classes (like ODSReader, ODTReader) to parse .ods, .odt, or other OpenDocument files from untrusted sourcesAffected if Your application uses jOpenDocument to parse ODF files from external or untrusted input
-
Check XML parser configuration for external entity settingsReview the XML parser setup in your code or framework configuration. Look for SAXParserFactory, DocumentBuilderFactory, or XMLReader instantiation. Inspect whether features 'http://xml.org/sax/features/external-general-entities' and 'http://xml.org/sax/features/external-parameter-entities' are explicitly set to falseAffected if External entity processing is not explicitly disabled (features are true, missing, or not configured) in the XML parser used by jOpenDocument
You are affected if jOpenDocument version 1.5 is in use AND your application parses untrusted ODF documents with external entity processing enabled in the XML parser.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable external entity processing in the XML parser configuration by setting feature 'http://xml.org/sax/features/external-general-entities' and 'http://xml.org/sax/features/external-parameter-entities' to false, or upgrade to a patched version if available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6501 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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