Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network/RF position
-
DeliverySniff cleartext UDP control traffic
-
ExploitForge or modify control packets (no integrity check)
-
ExecutionHijack or disrupt robot commands
-
ImpactLoss of operator control / robot manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V12 - Secure Communication Transport encryption
|
| Exploitation Conditions | Exploitation requires the attacker to be on the same adjacent network or RF segment as the robot (AV:A) and able to observe or inject the UDP control traffic between the operator control unit and a PackBot or FirstLook robot running the affected Aware2 software; the weakness is present because that control channel is transmitted in cleartext with no cryptographic integrity check, so no authentication, credentials, or user interaction are needed (PR:N/UI:N). Limiting factors: the attacker must achieve network/radio adjacency and timing to sniff or hijack live traffic, and the target must be an operational PackBot (≤6.9.0.2) or FirstLook (≤1.7.9) deployment - this is not remotely exploitable across the internet. |
| Impact | This is a genuine, well-grounded priority for organizations operating Teledyne FLIR PackBot or FirstLook robots, though the risk is bounded by the adjacency requirement. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N, score 8.5) indicates an adjacent-network, low-complexity, unauthenticated attack with no user interaction and high integrity/availability impact to both the vulnerable system (VI:H/VA:H) and subsequent systems (SI:H/SA:H) - consistent with the CWE-319 cleartext/no-integrity-check flaw in operator-to-robot UDP control traffic that permits interception, hijacking, and modification. Signals partially conflict on exploitation likelihood versus impact: there is no EPSS score, no CISA KEV listing, and no public exploit identified, so there is no evidence of active or widespread exploitation. The finding originates from Mandiant (a credible, high-rigor source), which raises confidence in its technical validity even absent a weaponized exploit. The adjacent vector (attacker must be on or near the same radio/network segment) and the niche, field-deployed nature of these robots make opportunistic mass exploitation unlikely; the realistic threat is targeted interference by an actor with proximity to the robot's RF/network link. Net: high technical severity with constrained real-world reach - not a drop-everything internet-facing emergency, but operationally serious wherever these platforms are in use. |
| Exploit ScenarioDerived | An attacker positioned on the same wireless/network segment as a PackBot or FirstLook robot passively sniffs the unencrypted, unauthenticated UDP control traffic between the operator control unit and the robot. Because the channel lacks a cryptographic integrity check, the attacker then injects or alters control packets to hijack movement or commands, or to disrupt the operator's control of the robot. No public exploit code is identified, but the attack requires only adjacency and low skill given the absence of any authentication or integrity protection. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated attackers on the same adjacent network or RF segment can intercept, hijack, or modify cleartext UDP control traffic to Teledyne FLIR PackBot and FirstLook robots running Aware2 (through 6.9.0.2 and 1.7.9 respectively) because the operator-control-unit-to-robot link lacks encryption and any cryptographic integrity check. The issue is rated CVSS 8.5 (AV:A/AC:L/PR:N/UI:N, with high integrity and availability impact) and requires network/radio adjacency plus timing to affect live operations; no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis. This is not an internet-reachable flaw and depends on the attacker being positioned to observe or inject the live UDP control stream.
RemediationAI
No vendor-released patch was identified at time of analysis, so operators should contact Teledyne FLIR directly for updated firmware and confirm whether an encrypted or authenticated control-link option is available for Aware2 on PackBot (6.9.0.2 and later) and FirstLook (1.7.9 and later). Until a fix is deployed, compensating controls should target the adjacency requirement: restrict RF coverage and physical access so that only authorized OCU operators can reach the robot's radio/network segment (directional antennas, reduced transmit power, RF shielding, and controlled operating areas), with the trade-off of limiting operational range and flexibility. Where the hardware and software support it, tunnel the control traffic through an encrypted and integrity-protected overlay such as IPsec or WireGuard between the OCU and the robot, accepting possible added latency and configuration/compatibility overhead; if the vendor protocol cannot be tunnelled cleanly, isolate the robot control network from any other systems and monitor for anomalous control commands, duplicated telemetry, or unexpected robot movement. Given the absence of public exploit code and KEV confirmation, prioritize these controls for deployments operating near untrusted populations or in contested RF environments, and reference the Mandiant disclosure at https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2026/MNDT-2026-0032.md alongside vendor guidance for updates.
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
CVE-2026-55396 is a cleartext-transmission weakness (CWE-319: Cleartext Transmission of Sensitive Information) in the UDP command channel that carries control traffic from a Teledyne FLIR operator control unit (OCU) to PackBot and FirstLook robots running the Aware2 software stack, tracked by CPE cpe:2.3:a:teledyne_flir:aware2:*:*:*:*:*:*:*:*. Because that link is neither encrypted nor protected by a cryptographic integrity check (such as a message authentication code or digital signature), any party able to receive or transmit on the same adjacent network or RF segment can read, replay, or forge control messages without possessing credentials or triggering user interaction. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N, with high integrity and availability impacts and lower confidentiality impact) and the independent CVSS 3.1 assessment (AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H) agree that the root cause is the absence of transport-layer protections and message authenticity rather than a memory-safety or logic bug. This is a design/protocol-level deficiency in the OCU-to-robot link; exploitation is bounded by the requirement for radio or Layer-2 adjacency and the need to act while the robot is under active control.
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:L/VI:H/VA:H/SC:L/SI:H/SA:H
Adjacent unauthenticated sniff/inject (AV:A/PR:N/UI:N/AC:L); cleartext exposure gives C:L while packet forgery hijacks the robot (I:H/A:H), a separate system from the control unit so S:C.
Primary rating from Vendor (Mandiant).
CVSS VectorVendor: Mandiant
DescriptionCVE.org
Cleartext transmission without a cryptographic integrity check in operator control unit to robot UDP traffic in Teledyne FLIR Aware2 versions through 6.9.0.2 (PackBot) and 1.7.9 (FirstLook) allows adjacent unauthenticated attackers to intercept, hijack, or modify control traffic against Teledyne FLIR PackBot and FirstLook robots running this software via sniffing or hijacking network traffic.
Executive ViewAI
Teledyne FLIR PackBot and FirstLook robots running Aware2 (versions up to 6.9.0.2 and 1.7.9 respectively) are exposed to unauthenticated attackers on the same adjacent network or RF segment, who can intercept, hijack, or modify cleartext UDP control traffic. This could disrupt live robotic operations, compromising mission integrity and availability. Leadership should prioritize mitigation because these robots are often deployed in critical environments where operational continuity and safety are paramount.
No vendor-released patch identified at time of analysis. Interim mitigations include strict network segmentation to isolate robot control traffic from untrusted networks, RF isolation and physical security to prevent adjacency, monitoring for unauthorized UDP traffic, and use of encrypted tunnels or VPNs for control links where feasible.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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 denial of service against Teledyne FLIR PackBot robots running the Aware2 web interface, where the reboo
Cleartext 802.11 session traffic between Teledyne FLIR Aware2 (versions through 6.9.0.2) and PackBot robots can be sniff
EUVD-2026-91053
GHSA-g94x-cw56-c3mr
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB