CVE-2026-66090

validatingZero is analyzing and reversing it now.

GHSA-555x-f7vj-p9qw ↗EUVD-2026-112566 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Apereo Foundation openEQUELLA < 2026.1
fixed in 2026.1
CWE-611 Improper Restriction of XML External Entity Reference
ETK-2026-2932Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 09mrunning
patch analysiscurrent stage
timeline
0 = cve.org publication
trigger signal (cve.org) +0hvalidating
0
+1h
+2h
+3h
+4h
+5h

description

openEQUELLA versions before 2026.1 process item metadata XML with external entities enabled. An attacker with CREATE_ITEM permission may cause the service to access local readable files or make outbound requests to chosen destinations.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade openEQUELLA to version 2026.1 or later. Until upgraded, limit CREATE_ITEM permission to trusted users.

fixed in 2026.1

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 09m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 01:37Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-29 01:37Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-66090

{
  "etk_id": "ETK-2026-2932",
  "cve_id": "CVE-2026-66090",
  "display_id": "CVE-2026-66090",
  "ghsa_id": "GHSA-555x-f7vj-p9qw",
  "euvd_id": "EUVD-2026-112566",
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "XML external entity injection in openEQUELLA metadata handling",
  "summary": "openEQUELLA versions before 2026.1 process item metadata XML with external entities enabled. An attacker with CREATE_ITEM permission may cause the service to access local readable files or make outbound requests to chosen destinations.",
  "mitigation": "Upgrade openEQUELLA to version 2026.1 or later. Until upgraded, limit CREATE_ITEM permission to trusted users.",
  "vendor": "Apereo Foundation",
  "product": "openEQUELLA",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.1"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.1"
      ],
      "package_name": "openEQUELLA",
      "purl": null
    }
  ],
  "cwes": [
    611
  ],
  "cvss_score": 7.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 76.01458243333333,
  "t0_at": "2026-10-29T01:37:37.928000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T01:37:37.928000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T01:37:37.928000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-66090"
    }
  }
}

published 2026-10-29 02:20Z
last change 2026-10-29 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.