Exploited CVEs / CVE-2026-34910

CVE-2026-34910

Ubiquiti UniFi OS Improper Input Validation Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2026-06-26 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

Risk summary

CriticalCISA KEV
10.0
CVSS v3 base
87%
EPSS exploit probability
Critical
Severity
2026-06-23
Added to KEV
2026-06-26 (past due)
CISA due date

Actively exploited Ubiquiti UniFi OS vulnerability, Critical severity, CVSS v3 10.0. Added to the CISA KEV catalog 2026-06-23.

Senserva AI read on CVE-2026-34910CISA required actionOfficial fix for CVE-2026-34910Admin questions

Senserva AI Opinion for CVE-2026-34910

This is a maximum-severity (CVSS 10.0) command injection flaw in Ubiquiti UniFi OS, the platform running UniFi Dream Machines, Cloud Keys, and network controllers. Anyone on the network can inject commands with no authentication described, and with an 87% EPSS score plus confirmed CISA KEV exploitation since 2026-06-23, attacks are already happening. Because UniFi OS often manages the network gateway itself, a compromise hands an attacker control of your perimeter.

Do this: Patch all UniFi OS devices to the latest firmware today and restrict management interface access to trusted VLANs or VPN until confirmed updated.

AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-34910

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Patch now
Exploited in the wild: confirmed by the CISA KEV catalog, not predicted.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Federal remediation deadline 2026-06-26; treat it as your outer bound. Patch now and verify deployment on every exposed device.

Updated August 19, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Full tracking and change history for CVE-2026-34910

Published
2026-06-23
Last revised
2026-06-23
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

Senserva Watchevery change we have recorded for this one
What changed, and when

The strongest signal is CVE-2026-34910's addition to the CISA KEV catalog on 2026-06-23, confirming active exploitation. On 2026-07-17 its Severity was scored at the maximum 10.0 with EPSS at 78.5%, which then rose to 87.0% by 2026-07-24. Known exploitation plus climbing exploit probability means prioritize remediation today.

0%25%50%75%100%CISA KEVCISA KEV on 2026-06-232026-07-17: EPSS 79%2026-07-17: EPSS 79%2026-07-24: EPSS 87%2026-07-24: EPSS 87%EPSS 87%2026-06-232026-07-24

Drawn by Senserva Vivid from the Senserva change record. Hover any point for its date and value.

  • 2026-06-23 added to the CISA KEV catalog by CISA
  • 2026-07-17 CVSS 0.0 to 10.0; EPSS first scored at 78.5%
  • 2026-07-24 EPSS 78.5% to 87.0%

Recorded by Senserva on the dates shown, from CISA KEV and FIRST EPSS. This is what moved and when, which neither the vendor advisory nor NVD publishes.

CISA required action

Federal (BOD 22-01) remediation due date: 2026-06-26 (past due).

Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

Official fix for CVE-2026-34910

Check the vendor's security advisory channel for the patched UniFi OS versions and workarounds.

Common questions about CVE-2026-34910

Is CVE-2026-34910 actively exploited?

Yes. CVE-2026-34910 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2026-06-23, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 87%.

What is the CISA deadline and required action for CVE-2026-34910?

CISA set the federal (BOD 22-01) remediation due date at 2026-06-26, which has passed; treat any unremediated system as overdue. The verbatim required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

What fixes CVE-2026-34910?

Check the vendor's security advisory for the patched UniFi OS versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2026-34910?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-34910's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (5 AM and 3 PM US Central).

Scope and sources

More exploited Ubiquiti CVEs
Authoritative references

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
Provided as is, without warranty; verify against the vendor advisory before acting. Data notice and terms.