CVE-2026-119249

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

GHSA-425j-mvh2-j6mf ↗EUVD-2026-113327 ↗

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.
Ubiquiti Inc WiFiman Desktop for macOS < 1.3.0
fixed in 1.3.0
CWE-1327 Binding to an Unrestricted IP Address
ETK-2026-2997Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 30msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h41m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

WiFiman Desktop for macOS is affected by an unrestricted IP address binding issue. An attacker with network access may obtain information about the host device; the advisory identifies network access as the stated precondition.

mitigation

Update WiFiman Desktop for macOS to version 1.3.0 or later. Until the update is deployed, limit untrusted devices' access to the affected host's network services.

fixed in 1.3.0

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
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-29 18:23Z
Δ 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-10-29 18:23Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2997",
  "cve_id": "CVE-2026-119249",
  "display_id": "CVE-2026-119249",
  "ghsa_id": "GHSA-425j-mvh2-j6mf",
  "euvd_id": "EUVD-2026-113327",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unrestricted IP address binding in WiFiman Desktop for macOS",
  "summary": "WiFiman Desktop for macOS is affected by an unrestricted IP address binding issue. An attacker with network access may obtain information about the host device; the advisory identifies network access as the stated precondition.",
  "mitigation": "Update WiFiman Desktop for macOS to version 1.3.0 or later. Until the update is deployed, limit untrusted devices' access to the affected host's network services.",
  "vendor": "Ubiquiti Inc",
  "product": "WiFiman Desktop for macOS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.3.0"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.3.0"
      ],
      "package_name": "WiFiman Desktop for macOS",
      "purl": null
    }
  ],
  "cwes": [
    1327
  ],
  "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": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.930685383333334,
  "t0_at": "2026-10-29T18:23:36.670000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-29T18:23:36.670000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-29T18:23:36.670000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-119249"
    }
  }
}

published 2026-10-29 18:44Z
last change 2026-10-29 22:04Z

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.