CVE-2026-107699

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

GHSA-hqhf-w97p-6w2f ↗EUVD-2026-95145 ↗

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.
tzwm ppt2png <= 0.0.6
ETK-2026-1015Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/ppt2png
12d 06h 36msince last run
9mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h33m
0
+2h
+6h
+8h
+10h
+12h

description

ppt2png through version 0.0.6 is affected by OS command injection in its handling of input and output path arguments. An attacker who can supply those path values may cause commands to run with the privileges of the Node.js process.

mitigation

Prevent untrusted users from controlling input or output path arguments, and strictly allow-list or validate accepted paths before invoking ppt2png. Run the service with least-privileged permissions and isolate it from sensitive systems.

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.
1.5%73rd percentile
agent run time
9m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 18: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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-08 18:36Z
    ghsa: trigger signal, started the run
  2. 2026-10-08 18:36Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1015",
  "cve_id": "CVE-2026-107699",
  "display_id": "CVE-2026-107699",
  "ghsa_id": "GHSA-hqhf-w97p-6w2f",
  "euvd_id": "EUVD-2026-95145",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OS command injection in ppt2png",
  "summary": "ppt2png through version 0.0.6 is affected by OS command injection in its handling of input and output path arguments. An attacker who can supply those path values may cause commands to run with the privileges of the Node.js process.",
  "mitigation": "Prevent untrusted users from controlling input or output path arguments, and strictly allow-list or validate accepted paths before invoking ppt2png. Run the service with least-privileged permissions and isolate it from sensitive systems.",
  "vendor": "tzwm",
  "product": "ppt2png",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 0.0.6"
      ],
      "ecosystem": "npm",
      "fixed_versions": [],
      "package_name": "ppt2png",
      "purl": "pkg:npm/ppt2png"
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0147,
  "epss_percentile": 0.7338,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 8.597831466666667,
  "t0_at": "2026-10-08T18:36:35.066000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T18:36:35.066000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T18:36:35.066000+00:00",
      "url": "https://github.com/advisories/GHSA-hqhf-w97p-6w2f"
    }
  }
}

published 2026-10-08 23:00Z
last change 2026-10-21 04:45Z

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.