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

CVE-2026-3511

HIGH · 8.6 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Restriction of XML External Entity Reference vulnerability in XMLUtils.java in Slovensko.Digital Autogram allows remote unauthenticated attacker to conduct SSRF (Server Side Request Forgery) attacks and obtain unauthorized access to local files on filesystems running the vulnerable application. Successful exploitation requires the victim to visit a specially crafted website that sends request containing a specially crafted XML document to /sign endpoint of the local HTTP server run by the application.

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

This is an XXE (XML External Entity) vulnerability in XMLUtils.java of the Slovensko.Digital Autogram application. The /sign endpoint parses XML documents without properly restricting external entity references, allowing attackers to embed malicious XXE payloads that trigger SSRF requests to internal services or read local files from the server's filesystem.

MitigationDisable external entity resolution and DTD processing in the XML parser configuration within XMLUtils.java. Use a secure XML parser factory with features like XMLConstants.FEATURE_SECURE_PROCESSING enabled and disable DOCTYPE declarations.

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

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

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 the application and version containing XMLUtils.java
    Locate XMLUtils.java in your deployment and determine the parent application name and version. Common locations include source code repositories, WAR files, or application binaries. Check the application JAR/WAR manifest or build metadata for version information.
    Affected if The application version falls within the vulnerable range for CVE-2026-3511 (compare your installed version to the affected ranges provided by the vendor).
  2. Verify the /sign endpoint is exposed
    Check your application's routing configuration or web.xml to confirm the /sign endpoint is registered and publicly or internally accessible. Attempt a HEAD or GET request to the endpoint if testing is authorized.
    Affected if The /sign endpoint is active and reachable without authentication.
  3. Inspect XMLUtils.java for XXE protections
    Examine the source code of XMLUtils.java and locate the XML parsing configuration. Look for whether the XMLParser or DocumentBuilder is configured with features like 'disallow-doctype-decl', 'external-general-entities', or 'external-parameter-entities' set to false, or whether DTD processing is disabled.
    Affected if XMLUtils.java does not explicitly disable external entity processing or DTD declarations; the XML parser accepts external entities.
  4. Check XML parser configuration settings
    Review the XML parsing implementation in XMLUtils.java for the DocumentBuilderFactory or XMLStreamReader setup. Verify if factory.setFeature() calls explicitly disable XXE vectors, or if security-aware parser configurations are applied.
    Affected if The XML parser configuration lacks explicit XXE protection (no feature settings to prevent external entity resolution).

Your environment is affected if the application contains a vulnerable version of XMLUtils.java, the /sign endpoint is accessible, and the XML parser is configured to allow external entity processing.

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 and DTD processing in the XML parser configuration within XMLUtils.java. Use a secure XML parser factory with features like XMLConstants.FEATURE_SECURE_PROCESSING enabled and disable DOCTYPE declarations.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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