CVE-2026-47097

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

GHSA-pp2h-qx3j-9gxh ↗EUVD-2026-89967 ↗

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.
AJA Video Systems HELO Plus < 2.1.7
fixed in 2.1.7
ETK-2026-172, permanent identifier
20d 08h 45msince last run
1h 09mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+10h37m
0
+2h
+4h
+6h
+8h
+12h

description

AJA HELO Plus devices running firmware earlier than 2.1.7 may expose diagnostic bundles containing sensitive system information. An unauthenticated attacker can retrieve and decrypt those bundles where the device's diagnostics endpoint is reachable.

mitigation

Upgrade AJA HELO Plus firmware to version 2.1.7 or later. Until upgrades are complete, restrict unauthenticated access to the diagnostics endpoint and limit network reachability to trusted administrators.

fixed in 2.1.7

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.38%30th percentile
agent run time
1h 09m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-30 14:31Z
Δ 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-09-30 14:31Z
    ghsa: trigger signal, started the run
  2. 2026-09-30 14:31Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-172",
  "cve_id": "CVE-2026-47097",
  "display_id": "CVE-2026-47097",
  "ghsa_id": "GHSA-pp2h-qx3j-9gxh",
  "euvd_id": "EUVD-2026-89967",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated diagnostic bundle disclosure in AJA HELO Plus",
  "summary": "AJA HELO Plus devices running firmware earlier than 2.1.7 may expose diagnostic bundles containing sensitive system information. An unauthenticated attacker can retrieve and decrypt those bundles where the device's diagnostics endpoint is reachable.",
  "mitigation": "Upgrade AJA HELO Plus firmware to version 2.1.7 or later. Until upgrades are complete, restrict unauthenticated access to the diagnostics endpoint and limit network reachability to trusted administrators.",
  "vendor": "AJA Video Systems",
  "product": "HELO Plus",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.1.7"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.1.7"
      ],
      "package_name": "HELO Plus",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
  "epss_score": 0.0038,
  "epss_percentile": 0.308,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 68.6385399,
  "t0_at": "2026-09-30T14:31:11.797000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T14:31:11.797000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-30T14:31:11.797000+00:00",
      "url": "https://github.com/advisories/GHSA-pp2h-qx3j-9gxh"
    }
  }
}

published 2026-09-30 23:59Z
last change 2026-10-21 09:11Z

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.