Is this vulnerability remotely exploitable?

Yes. An attacker can remotely exploit the issue by luring a victim into visiting a specially crafted website that causes the victim's browser or environment to send malicious XML to the Autogram `/sign` endpoint.

Does the attacker need authenticated access to Autogram?

No explicit authenticated access to the vulnerable endpoint is required, based on the description. The main requirement is that the victim has a running Autogram instance accessible via its local HTTP server and that the attacker can induce requests to it.

What is the safest general fix pattern?

The safest pattern is to harden all XML parsing by disabling external entity resolution and DTD processing in `XMLUtils.java`, and ensuring any XML library is configured with secure defaults. Where possible, migrate away from XML for untrusted input or strictly validate against controlled schemas without external references.

Severity:

HIGH RISK

(8.6)

XML External Entity (XXE) Injection (CWE-611) in Autogram XML Processing

CVE-2026-3511

Published:

Mar 19, 2026

Status:

Awaiting Analysis

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

XML External Entity (XXE) Injection

CWE:

CWE-611

Impact:

Server-Side Request Forgery and Local File Disclosure

Severity:

HIGH RISK

(8.6)

CVSS Version:

3.1

Vulnerability Type

Category:

XML External Entity (XXE) Injection

CWE:

CWE-611

Impact:

Server-Side Request Forgery and Local File Disclosure

Severity:

HIGH RISK

(8.6)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

XML External Entity (XXE) Injection (CWE-611) in Autogram XML Processing

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal