CVE-2026-132805

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

GHSA-6m7j-cqmc-p88h ↗EUVD-2026-129460 ↗

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 UniFi Access Application < 4.3.24
fixed in 4.3.24
CWE-918 Server-Side Request Forgery (SSRF)
ETK-2026-4883Zero's internal tracking ID, independent of the CVE number., permanent identifier
9h 38msince last run
1h 13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+3h51m
0
+2h
+6h
+8h
+10h
+12h

description

UniFi Access Application contains a server-side request forgery vulnerability. An attacker able to reach the application over the network may cause unauthorized requests that expose host-device information or make unauthorized changes.

mitigation

Upgrade UniFi Access Application to version 4.3.24 or later. Restrict network access to the application to trusted administrative networks until the update is installed.

fixed in 4.3.24

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
1h 13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-19 04:32Z
Δ 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-19 04:32Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4883",
  "cve_id": "CVE-2026-132805",
  "display_id": "CVE-2026-132805",
  "ghsa_id": "GHSA-6m7j-cqmc-p88h",
  "euvd_id": "EUVD-2026-129460",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Server-side request forgery in UniFi Access Application",
  "summary": "UniFi Access Application contains a server-side request forgery vulnerability. An attacker able to reach the application over the network may cause unauthorized requests that expose host-device information or make unauthorized changes.",
  "mitigation": "Upgrade UniFi Access Application to version 4.3.24 or later. Restrict network access to the application to trusted administrative networks until the update is installed.",
  "vendor": "Ubiquiti Inc",
  "product": "UniFi Access Application",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 4.3.24"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.3.24"
      ],
      "package_name": "UniFi Access Application",
      "purl": null
    }
  ],
  "cwes": [
    918
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 73.48804371666667,
  "t0_at": "2026-11-19T04:32:30.374000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-19T04:32:30.374000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-19T04:32:30.374000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-132805"
    }
  }
}

published 2026-11-19 05:21Z
last change 2026-11-19 17:22Z

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.