Skip to content
Applications

CVE-2026-82880

8.7
High
EPSS 0.34%Patch availableSep 1, 2026

XXE in YaCy parsers allows local file exposure via crafted documents

common questions

Is CVE-2026-82880 being exploited?

Not confirmed. CVE-2026-82880 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-82880?

CVE-2026-82880 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-82880?

Yes. A fix has been recorded for CVE-2026-82880. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-82880 affect?

CVE-2026-82880 affects YaCy Search Server <= 1.941, SVG parser, FreeMind (mm) parser, OpenSearch parser. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-82880?

Upgrade YaCy to a patched release (>1.941) or apply the commit; disable external entity resolution.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
YaCy Search Server <= 1.941SVG parserFreeMind (mm) parserOpenSearch parser
impact

XML External Entity (XXE) lets attackers supply documents that cause the crawler to read local files and index/exfiltrate their contents.

action required

Immediate action required

affected versions
yacy yacy_search_server
  • affected<= 1.941
vendor says fixed in3c3a307e8b7a0ebbc4d1e6b10898b52e15c0cd44

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free