CVE-2026-104020

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

GHSA-93q6-f8hx-vv7f ↗EUVD-2026-91059 ↗

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.
Amazon ion-python < 0.15.0
fixed in 0.15.0
CWE-674 Uncontrolled Recursion
ETK-2026-287, permanent identifier
19d 15h 00msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h49m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Amazon ion-python versions before 0.15.0 are affected by uncontrolled recursion while reading deeply nested Ion values. A remote unauthenticated attacker may cause an application using the library to crash if it processes attacker-supplied Ion data, resulting in denial of service.

mitigation

Upgrade ion-python to version 0.15.0 or later. Until upgraded, limit or reject untrusted deeply nested Ion input where possible.

fixed in 0.15.0

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.
0.44%36th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 20:36Z
Δ 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-10-01 20:36Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-287",
  "cve_id": "CVE-2026-104020",
  "display_id": "CVE-2026-104020",
  "ghsa_id": "GHSA-93q6-f8hx-vv7f",
  "euvd_id": "EUVD-2026-91059",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncontrolled recursion denial of service in ion-python",
  "summary": "Amazon ion-python versions before 0.15.0 are affected by uncontrolled recursion while reading deeply nested Ion values. A remote unauthenticated attacker may cause an application using the library to crash if it processes attacker-supplied Ion data, resulting in denial of service.",
  "mitigation": "Upgrade ion-python to version 0.15.0 or later. Until upgraded, limit or reject untrusted deeply nested Ion input where possible.",
  "vendor": "Amazon",
  "product": "ion-python",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.15.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.15.0"
      ],
      "package_name": "ion-python",
      "purl": null
    }
  ],
  "cwes": [
    674
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0044,
  "epss_percentile": 0.3697,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.41610605,
  "t0_at": "2026-10-01T20:36:33.967000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-01T20:36:33.967000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T20:36:33.967000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104020"
    }
  }
}

published 2026-10-01 23:11Z
last change 2026-10-21 13:29Z

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.