Skip to main content
VulnerabilityPublished Updated

CVE-2025-45583: Audi UTR · Improper Authentication

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Immediate mitigation should focus on network-level controls to restrict access to the vulnerable FTP service. Organizations should implement strict firewall rules to limit FTP access only to trusted management networks or devices. Network segmentation should isolate the Audi UTR 2.0 devices from general user networks and the internet. Monitoring network traffic for unusual FTP connection attempts or unauthorized access patterns is recommended. Since no patches are currently available, organizations should consider disabling the FTP service on these devices if operationally feasible or replacing the device with a more secure alternative. If disabling FTP is not possible, deploying an application-layer firewall or FTP proxy that enforces authentication could help mitigate unauthorized access. Additionally, organizations should review and harden access credentials and audit logs for suspicious activity. Planning for rapid deployment of vendor patches or firmware updates once released is critical. Finally, organizations should conduct a risk assessment to identify all Audi UTR 2.0 devices in their environment and prioritize remediation efforts accordingly.

Description

Incorrect access control in the FTP protocol of Audi UTR 2.0 Universal Traffic Recorder 2.0 allows attackers to authenticate into the service using any combination of username and password.

References

Community reviews

Loading reviews…