ETK-2026-3011Zero's internal tracking ID, independent of the CVE number.

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

GHSA-jr9g-hfqp-pv83 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
github composer:WWBN/AVideo-Encoder v8.4.0; master through f05d252 (earlier versions not fully assessed)
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-3011Zero's internal tracking ID, independent of the CVE number., no cve assigned
2h 32msince last run
50mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+0h37m
0
+1h
+2h
+3h

description

AVideo-Encoder's watermark endpoint is affected by an OS command injection flaw. An unauthenticated remote attacker may run commands with the web server's account privileges when the endpoint is accessible.

mitigation

Block public access to view/watermark.php at the web server or reverse proxy, or allow only trusted clients. Apply an upstream patched release when one is published.

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
50m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-29 22:01Z

this entry in the feed

GET /api/v1/feed/ETK-2026-3011

{
  "etk_id": "ETK-2026-3011",
  "cve_id": null,
  "display_id": "ETK-2026-3011",
  "ghsa_id": "GHSA-jr9g-hfqp-pv83",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "OS command injection in AVideo-Encoder watermark handler",
  "summary": "AVideo-Encoder's watermark endpoint is affected by an OS command injection flaw. An unauthenticated remote attacker may run commands with the web server's account privileges when the endpoint is accessible.",
  "mitigation": "Block public access to `view/watermark.php` at the web server or reverse proxy, or allow only trusted clients. Apply an upstream patched release when one is published.",
  "vendor": "github",
  "product": "composer:WWBN/AVideo-Encoder",
  "affected": [
    {
      "affected_notes": [
        "master through f05d252 (earlier versions not fully assessed)"
      ],
      "affected_ranges": [
        "v8.4.0"
      ],
      "ecosystem": "github",
      "fixed_versions": [],
      "package_name": "WWBN/AVideo-Encoder",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 49.69986986666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T22:01:17+00:00",
      "days": -0.13129295498842591,
      "is_lower_bound": true,
      "measured_at": "2026-10-30T01:10:20.740518+00:00",
      "url": "https://github.com/WWBN/AVideo-Encoder/security/advisories/GHSA-jr9g-hfqp-pv83"
    }
  }
}

published 2026-10-29 22:15Z
last change 2026-10-30 01:09Z

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.