CVE-2026-8372

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

GHSA-p43j-wrmf-984c ↗EUVD-2026-120777 ↗

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.
Axis Communications AB AXIS Camera Station Pro >= 6.13, < 6.18
fixed in 6.18
CWE-306 Missing Authentication for Critical Function
ETK-2026-4029Zero's internal tracking ID, independent of the CVE number., permanent identifier
1d 00h 30msince last run
27mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h38m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

AXIS Camera Station Pro versions before 6.18 contain an issue that could permit unauthorized access. The available evidence does not identify the affected function or the conditions an attacker must meet.

mitigation

Update AXIS Camera Station Pro to version 6.18. Until the update is deployed, limit access to the Camera Station Pro environment to trusted users and networks.

fixed in 6.18

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.
–
agent run time
27m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 05: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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-10 05:36Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4029",
  "cve_id": "CVE-2026-8372",
  "display_id": "CVE-2026-8372",
  "ghsa_id": "GHSA-p43j-wrmf-984c",
  "euvd_id": "EUVD-2026-120777",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthorized access vulnerability in AXIS Camera Station Pro",
  "summary": "AXIS Camera Station Pro versions before 6.18 contain an issue that could permit unauthorized access. The available evidence does not identify the affected function or the conditions an attacker must meet.",
  "mitigation": "Update AXIS Camera Station Pro to version 6.18. Until the update is deployed, limit access to the Camera Station Pro environment to trusted users and networks.",
  "vendor": "Axis Communications AB",
  "product": "AXIS Camera Station Pro",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 6.13, < 6.18"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "6.18"
      ],
      "package_name": "AXIS Camera Station Pro",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 27.207471883333334,
  "t0_at": "2026-11-10T05:36:58.926000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T05:36:58.926000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T05:36:58.926000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-8372"
    }
  }
}

published 2026-11-10 05:48Z
last change 2026-11-11 05: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.