dbcve.org
XmlbeansApplication · Apache

CVE-2021-23926

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-14
Fix available
A fix is available. Upgrade to after 2.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 XML parsers used by XMLBeans up to version 2.6.0 did not set the properties needed to protect the user from malicious XML input. Vulnerabilities include possibilities for XML Entity Expansion attacks. Affects XMLBeans up to and including v2.6.0.

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

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XmlbeansApplication
Affected:<= 2.6.0
Debian LinuxOperating system
Affected:= 9.0
Oncommand Unified Manager Core PackageApplication
Affected:all versions
Snap Creator FrameworkApplication
Affected:all versions
SnapmanagerApplication
Affected:all versions
Middleware Common Libraries And ToolsApplication
Affected:= 12.2.1.3.0= 12.2.1.4.0
Peoplesoft Enterprise PeopletoolsApplication
Affected:= 8.57= 8.58= 8.59

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.6.0
Vendor patch www.oracle.com →
Recommended fix High confidence

XMLBeans 3.0.0 or later (e.g., 3.1.0, 4.0.0)

  1. Identify all applications and dependencies that use XMLBeans version 2.6.0 or earlier by reviewing project dependencies (Maven pom.xml, Gradle build files, or JAR manifests)
  2. Locate the XMLBeans library in your application's classpath or bundled libraries
  3. Upgrade XMLBeans to version 3.0.0 or later (e.g., 3.1.0, 4.0.0) by updating the dependency in your build configuration (Maven: change version in pom.xml, Gradle: update version in build.gradle)
  4. Rebuild and recompile the application to include the new XMLBeans library
  5. Test the application to ensure XML parsing functionality works correctly with the upgraded library
  6. Redeploy the updated application to all affected environments
Caveat Minor - XMLBeans 3.0.0 introduced some API changes; review migration notes for any deprecated method usage in your code

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-23926 — 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-2021-23926 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