Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-82880 – XXE Information Disclosure – YaCy Search Server ≤ 1.941

Be the first to know when new zero-days emerge:

Summary

CVE-2026-82880 is an XML External Entity (XXE) injection vulnerability in YaCy Search Server through version 1.941. Multiple XML parsers used by the crawler fail to disable external entity resolution, allowing a remote, unauthenticated attacker to exfiltrate local file contents from the server. The flaw is rated HIGH severity.

Technical details

  • Root cause: YaCy’s SAX-based XML parsers (used by the SVG, FreeMind/MM, and OpenSearch description parsers) instantiate SAXParserFactory without hardening setFeature() calls, leaving DOCTYPE and external entity resolution enabled.
  • Trigger conditions: An attacker publishes a document (e.g., a crafted SVG, FreeMind, or OpenSearch description file) containing a DOCTYPE declaration with a SYSTEM entity pointing to a local file path.
  • Attack vector: Network-reachable via YaCy’s crawl pipeline — no authentication or user interaction required. When YaCy crawls and indexes the malicious document, the vulnerable parser resolves the external entity.
  • Impact: Contents of local files (e.g., /etc/passwd or other server-readable files) can be read and exfiltrated into the search index, resulting in confidentiality loss. No impact to integrity or availability was reported.

Affected software

  • YaCy Search Server: all versions through 1.941 (inclusive)

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade to a YaCy Search Server build that includes the fix committed at 3c3a307e8b7a0ebbc4d1e6b10898b52e15c0cd44, which disables DOCTYPE declarations and external general/parameter entities in the affected parsers.
  • If no patch is available yet: Restrict or disable crawling of untrusted domains and untrusted document uploads (SVG, FreeMind, OpenSearch description files); block outbound network access from the YaCy host to reduce exfiltration paths; monitor for crawler requests to unexpected local file paths.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: YaCy 'search page name': Search Page

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge