# CVE-2026-55395: Hardcoded Passwords in Teledyne FLIR Robots running Aware2

> Remote attackers can access and reconfigure Teledyne FLIR PackBot and FirstLook robots by using hardcoded passwords found in firmware or documentation.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Oct 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-r959-63hv-grw3

## What is CVE-2026-55395?

CVE-2026-55395 is a critical vulnerability in Teledyne FLIR Aware2, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Hardcoded passwords in the access control in Teledyne FLIR Aware2 versions through 6.9.0.2 (PackBot) and 1.7.9 (FirstLook) allows remote unauthenticated attackers to access and reconfigure Teledyne FLIR PackBot and FirstLook robots running this software via reading the passwords from the firmware or documentation.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-55395?


## How do I fix CVE-2026-55395?

No fix has been published for CVE-2026-55395 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55395 being exploited?

There is no known exploitation of CVE-2026-55395 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55395 and fix it if it is affected.

What it is: CVE-2026-55395 is a critical vulnerability in Teledyne FLIR Aware2, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55395 in the wild and no public exploit code.

Affected product: Teledyne FLIR Aware2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55395/ (Markdown: https://insights.sbomify.com/CVE-2026-55395/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55395
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55395
- OSV: https://osv.dev/vulnerability/CVE-2026-55395

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55395/
Summaries are generated and may contain mistakes; the official description above is the record.