CVE-2026-105105

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

GHSA-9xfm-37f4-2h8g ↗EUVD-2026-92014 ↗

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.
nasa-ammos AIT-Core <= 3.1.1
ETK-2026-455, permanent identifier
pkg:pypi/ait-core
18d 02h 00msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h40m
0
+4h
+6h
+8h
+10h
+12h

description

AIT-Core ait-server installations through 3.1.1 may expose the ZeroMQ telemetry and command broker without access controls. An unauthenticated party that can reach that broker may read, forge, inject, or interfere with command and telemetry traffic.

mitigation

Upgrade AIT-Core to version 3.1.2. Until upgraded, restrict ZeroMQ broker access to trusted local or management networks and block untrusted connections to its message-bus ports.

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.78%55th percentile
agent run time
18m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-03 11:55Z
Δ 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-03 11:55Z
    ghsa: trigger signal, started the run
  2. 2026-10-03 11:55Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-455",
  "cve_id": "CVE-2026-105105",
  "display_id": "CVE-2026-105105",
  "ghsa_id": "GHSA-9xfm-37f4-2h8g",
  "euvd_id": "EUVD-2026-92014",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in AIT-Core telemetry and command broker",
  "summary": "AIT-Core ait-server installations through 3.1.1 may expose the ZeroMQ telemetry and command broker without access controls. An unauthenticated party that can reach that broker may read, forge, inject, or interfere with command and telemetry traffic.",
  "mitigation": "Upgrade AIT-Core to version 3.1.2. Until upgraded, restrict ZeroMQ broker access to trusted local or management networks and block untrusted connections to its message-bus ports.",
  "vendor": "nasa-ammos",
  "product": "AIT-Core",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.1.1"
      ],
      "ecosystem": "pypi",
      "fixed_versions": [],
      "package_name": "ait-core",
      "purl": "pkg:pypi/ait-core"
    }
  ],
  "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.0078,
  "epss_percentile": 0.5528,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.35923225,
  "t0_at": "2026-10-03T11:55:44.853000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-03T11:55:44.853000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-03T11:55:44.853000+00:00",
      "url": "https://github.com/advisories/GHSA-9xfm-37f4-2h8g"
    }
  }
}

published 2026-10-03 13:17Z
last change 2026-10-21 05:31Z

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.