CVE-2026-123816

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

GHSA-r44w-v6gf-x3p6 ↗EUVD-2026-120452 ↗

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.
pyload 0.5.0b3
fixed in 0.5.0b3.dev101
CWE-287 Improper Authentication
ETK-2026-3997Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/pyload
1d 08h 32msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h58m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

pyLoad versions before 0.5.0b3.dev101 can accept an invalid API key when its identifier matches a key recently used by a legitimate client. An unauthenticated remote attacker may gain the permissions of that key's owner if the relevant cache entry is still active.

mitigation

Upgrade pyLoad to version 0.5.0b3.dev101 or later. Until upgraded, restrict access to the API to trusted clients and networks to reduce exposure.

fixed in 0.5.0b3.dev101

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.
contextual
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
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-09 21:15Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-09 21:15Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3997",
  "cve_id": "CVE-2026-123816",
  "display_id": "CVE-2026-123816",
  "ghsa_id": "GHSA-r44w-v6gf-x3p6",
  "euvd_id": "EUVD-2026-120452",
  "status": "published",
  "anchor_state": "anchored",
  "title": "API key cache authentication bypass in pyLoad",
  "summary": "pyLoad versions before 0.5.0b3.dev101 can accept an invalid API key when its identifier matches a key recently used by a legitimate client. An unauthenticated remote attacker may gain the permissions of that key's owner if the relevant cache entry is still active.",
  "mitigation": "Upgrade pyLoad to version 0.5.0b3.dev101 or later. Until upgraded, restrict access to the API to trusted clients and networks to reduce exposure.",
  "vendor": "pyload",
  "product": "pyload",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "0.5.0b3"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "0.5.0b3.dev101"
      ],
      "package_name": "pyload",
      "purl": "pkg:pypi/pyload"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.203799033333333,
  "t0_at": "2026-11-09T21:15:48.314000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-09T21:15:48.314000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-09T21:15:48.314000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123816"
    }
  }
}

published 2026-11-09 22:00Z
last change 2026-11-11 05:12Z

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.