CVE-2026-130591

waiting for further signalsZero needs more public information before it can validate it.

GHSA-h7rf-8j2m-x5qj ↗EUVD-2026-127013 ↗

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.
53AI 53AIHub < 0.5.5
fixed in 0.5.5
CWE-306 Missing Authentication for Critical Function
ETK-2026-4675Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 07h 27msince last run
19mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h47m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

53AIHub versions earlier than 0.5.5 permit unauthenticated access to stored knowledge-base files and file versions. An attacker who can reach an affected deployment may retrieve content belonging to other enterprise tenants without an account.

mitigation

Upgrade 53AIHub to version 0.5.5 or later. Until upgraded, restrict network access to the affected service to trusted users and networks.

fixed in 0.5.5

check
no
exploit
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
19m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-17 13:52Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-11-17 13:52Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4675",
  "cve_id": "CVE-2026-130591",
  "display_id": "CVE-2026-130591",
  "ghsa_id": "GHSA-h7rf-8j2m-x5qj",
  "euvd_id": "EUVD-2026-127013",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication exposes files in 53AIHub",
  "summary": "53AIHub versions earlier than 0.5.5 permit unauthenticated access to stored knowledge-base files and file versions. An attacker who can reach an affected deployment may retrieve content belonging to other enterprise tenants without an account.",
  "mitigation": "Upgrade 53AIHub to version 0.5.5 or later. Until upgraded, restrict network access to the affected service to trusted users and networks.",
  "vendor": "53AI",
  "product": "53AIHub",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.5.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.5.5"
      ],
      "package_name": "53AIHub",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.048068783333335,
  "t0_at": "2026-11-17T13:52:13.445000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-17T13:52:13.445000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-17T13:52:13.445000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-130591"
    }
  }
}

published 2026-11-17 14:20Z
last change 2026-11-18 21:43Z

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.