Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network access to robot
-
ExploitSend unauthenticated request to reboot endpoint
-
ImpactRobot reboots, denial of service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network adjacency (CVSS AV:A) - the attacker must reach the Aware2 web interface on the local or adjacent network segment of a PackBot robot running Aware2 version 6.9.0.2 or earlier; this is NOT internet-remote. No authentication is required (PR:N) and no user interaction (UI:N) because the reboot endpoint lacks any authentication control (CWE-306). The specific prerequisite is reachability of the Aware2 web interface's reboot endpoint; the limiting factor is that the attacker must already hold a position on the adjacent network, which bounds exposure to operational/field networks rather than the open internet. Impact is confined to denial of service (robot reboot); there is no data exposure or code execution. |
| Impact | This is a genuine but bounded risk, best characterized as a moderate operational-availability issue rather than a top-tier emergency. The CVSS 4.0 vector (AV:A/AC:L/PR:N/UI:N, VA:H, score 7.1) confirms low-complexity, unauthenticated exploitation but critically specifies an ADJACENT network vector (AV:A) - not fully remote internet-facing access - so the attacker must already be on the same local/adjacent network segment as the PackBot robot. The only impact is availability (VA:H); there is no confidentiality or integrity loss (VC:N/VI:N), matching the CWE-306 missing-authentication DoS described. All exploitation signals point AWAY from urgency: SSVC rates Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial'; there is no CISA KEV listing and no public exploit identified at time of analysis, so this is 'no public exploit identified at time of analysis.' The signals are internally consistent rather than conflicting - the moderately high 7.1 is driven by the easy unauthenticated trigger and high availability impact, tempered by the adjacent-only vector. The practical priority is therefore elevated specifically for operators of FLIR PackBot fleets where an attacker could gain adjacent network access (e.g., field-deployed or shared operational networks), but it is low priority for general enterprise IT. No key data appears contradictory; the main missing element is any patched-version confirmation beyond 'through 6.9.0.2'. |
| Exploit ScenarioDerived | An attacker with access to the same local or adjacent network as a Teledyne FLIR PackBot robot sends an unauthenticated request to the Aware2 web interface's reboot endpoint, which lacks any authentication check. The robot reboots on demand, and repeated calls keep it offline, denying its availability during an operation. No public exploit code has been identified, and the low complexity (AC:L) means no special timing or conditions are required once network adjacency is achieved. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated denial of service against Teledyne FLIR PackBot robots running the Aware2 web interface, where the reboot endpoint is exposed without any authentication control. Attackers who already hold a position on the local or adjacent network segment (CVSS AV:A) can trigger a robot reboot with no credentials (PR:N) and no user interaction (UI:N), disrupting operational availability of the platform. According to our independent assessment, this is a genuine but bounded operational-availability issue rather than a top-tier emergency: exposure is confined to field/operational networks rather than the open internet, impact is limited to denial of service with no data exposure or code execution, and no public exploit had been identified at the time of analysis (Mandiant disclosure MNDT-2026-0027; EUVD-2026-91048).
RemediationAI
No vendor-released patch or fixed version is identified in the available data at time of analysis, so remediation must rely on compensating controls. The most effective measure is network scoping: keep the Aware2 web interface off any untrusted or broadly routed segment and enforce firewall/VLAN ACLs so that only authorized maintenance hosts on the robot's dedicated management segment can reach the reboot endpoint - the trade-off is added operational overhead for field maintenance and the need to maintain accurate firewall rules as robots are deployed. Where the reboot function is not required during operations, disable or block access to the reboot endpoint (or the web interface entirely) at the network layer, accepting that legitimate remote maintenance reboots will then require re-enabling the service or a local/manual procedure. Deploy the robots on isolated operational VLANs separate from general corporate or wireless networks to prevent a foothold on an adjacent segment from reaching the endpoint, noting that this reduces but does not eliminate risk from a compromised device already on that VLAN. Monitor and log requests to the Aware2 web interface for unexpected reboot calls to detect misuse, but recognize this is detection rather than prevention. Track the Mandiant disclosure (https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0027.md) and EUVD-2026-91048 for vendor advisory and patched firmware updates, and apply the vendor fix as soon as it becomes available. No public exploit code or confirmed active exploitation was identified at time of analysis.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-306 (Missing Authentication for Critical Function) in the web interface of Teledyne FLIR Aware2, the software component used on PackBot robots. The reboot endpoint, which is a critical operational function, is reachable without any credential check. The affected CPE is cpe:2.3:a:teledyne_flir:aware2:*:*:*:*:*:*:*:* with affected versions through 6.9.0.2 per the EUVD entry. The assessed vector (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) assigns high availability impact only, confirming the root cause is an access-control gap rather than memory corruption, injection, or cryptographic failure, and the CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) is consistent with this. The attack surface is deliberately bounded by network adjacency, meaning the flaw is exploitable from a position on the same or an adjacent network segment as the robot's Aware2 interface, not from the public internet.
Know when Aware2 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Adjacent vector (AV:A) per the disclosure, trivial unauthenticated trigger (AC:L/PR:N/UI:N) of an unprotected reboot endpoint, availability-only impact (A:H) with no C/I loss.
Primary rating from Vendor (Mandiant).
CVSS VectorVendor: Mandiant
DescriptionCVE.org
Missing authentication in the web interface in Teledyne FLIR Aware2 versions through 6.9.0.2 allows remote unauthenticated attackers to achieve denial of service against Teledyne FLIR PackBot robots running this software via misuse of the reboot endpoint.
Executive ViewAI
Teledyne FLIR PackBot robots running the Aware2 web interface can be rebooted by anyone who can reach the device from the same local or adjacent network segment, without any credentials or user interaction. Because these platforms are used in field operations, repeated or timed reboots could interrupt missions and force manual recovery, but the impact is confined to availability - there is no data exposure or code execution, and no public exploit code has been identified at time of analysis. Leadership should treat this as a contained operational-network risk rather than an enterprise-wide emergency.
No vendor-released patch identified at time of analysis. Interim mitigations: isolate PackBot Aware2 interfaces on dedicated operational VLANs, use firewall/ACL rules to block the reboot endpoint from all but authorized management hosts, restrict local and adjacent-network (including wireless) access to the robots, and monitor for anomalous or unexpected reboot events.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Unvalidated pathnames in the Teledyne FLIR Aware2 web interface let remote unauthenticated attackers read configuration
Hardcoded credentials in Teledyne FLIR Aware2 let unauthenticated attackers within radio or network adjacency (CVSS AV:A
Cleartext transmission in the primary control endpoints of Teledyne FLIR Aware2 (all versions through 6.9.0.2) allows an
Unauthenticated attackers on the same adjacent network or RF segment can intercept, hijack, or modify cleartext UDP cont
Cleartext 802.11 session traffic between Teledyne FLIR Aware2 (versions through 6.9.0.2) and PackBot robots can be sniff
EUVD-2026-91048
GHSA-qr3q-9g2p-q6vc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB