CVE-2026-63501

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

GHSA-6w3r-6hpr-hp6p ↗EUVD-2026-116262 ↗

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.
Agamnentzar ag-psd <= 31.0.0
fixed in 31.0.1
CWE-770 Allocation of Resources Without Limits or Throttling
ETK-2026-3402Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/ag-psd
1d 04h 04msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h58m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

ag-psd can exceed intended memory limits while decoding PSD layer data and decompressing ZIP-encoded channel data. An attacker who can provide a PSD to an application with layer decoding enabled may exhaust process memory and cause a denial of service.

mitigation

Upgrade ag-psd to version 31.0.1 or later. Until upgrading, avoid processing untrusted PSD files and disable layer decoding where feasible.

fixed in 31.0.1

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
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-03 19:30Z
Δ 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-03 19:30Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3402",
  "cve_id": "CVE-2026-63501",
  "display_id": "CVE-2026-63501",
  "ghsa_id": "GHSA-6w3r-6hpr-hp6p",
  "euvd_id": "EUVD-2026-116262",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Uncontrolled memory allocation in ag-psd PSD parsing",
  "summary": "ag-psd can exceed intended memory limits while decoding PSD layer data and decompressing ZIP-encoded channel data. An attacker who can provide a PSD to an application with layer decoding enabled may exhaust process memory and cause a denial of service.",
  "mitigation": "Upgrade ag-psd to version 31.0.1 or later. Until upgrading, avoid processing untrusted PSD files and disable layer decoding where feasible.",
  "vendor": "Agamnentzar",
  "product": "ag-psd",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 31.0.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "31.0.1"
      ],
      "package_name": "ag-psd",
      "purl": "pkg:npm/ag-psd"
    }
  ],
  "cwes": [
    770
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.304290216666667,
  "t0_at": "2026-11-03T19:30:03.984000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-03T19:30:03.984000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-03T19:30:03.984000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63501"
    }
  }
}

published 2026-11-03 20:15Z
last change 2026-11-04 14:42Z

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.