Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2025-34053

AVTECH IP camera, DVR, and NVR Devices Authentication Bypass via .cab Path Manipulation

Medium6.9Public exploitEPSS 0.63%
Published
Updated
Reserved
Assigned by
VulnCheck

Description

An authentication bypass vulnerability exists in AVTECH IP camera, DVR, and NVR devices’ streamd web server. The strstr() function is used to identify ".cab" requests, allowing any URL containing ".cab" to bypass authentication and access protected endpoints.

Public exploit

2 references of the record are tagged as an exploit or proof of concept: anyone can try it against an unpatched system. CISA's SSVC rates its exploitation: a proof of concept is public.

Timeline

  1. ID reserved

    By VulnCheck

  2. · 3 months later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-34053, by who scored it
Scored byCVSSScoreVector
VulnCheckCNA (assigner)4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0Medium6.9CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.63% · top 50% of all CVEs (7 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Weakness

Affected products

  • AVTECH · IP camera, DVR, and NVR devices

    • affected 1000-1000-1000-1000
    • affected 1000C-1000C-1000C-1000C
    • affected 1001-1000-1000-1000
    • affected 1001-1001-1000-1000
    • affected 1002-1000-1000-1000
    • affected 1002-1002-1000-1002
    • affected 1002D-1000D-1000D-1000D
    • affected 1003-1000-1000-1001
    • affected 1003-1001-1001-1000
    • affected 1003-1002-1001-1000
    • affected 1004-1000-1000-1000
    • affected 1004-1001-1001-1001
    • affected 1004-1003-1001-1002
    • affected 1004-1003-1002-1001
    • affected 1004A-1001A-1002A-1000A
    • affected 1005-1002-1001-1002
    • affected 1005-1003-1001-1002
    • affected 1005-1004-1002-1001
    • affected 1005A-1001A-1002A-1001A
    • affected 1005D-1001D-1002D-1001D
    • affected 1006-1002-1001-1002
    • affected 1006-1004-1003-1001
    • affected 1007-1001-1003-1001
    • affected 1007-1001-1004-1003
    • affected 1007-1002-1001-1003
    • affected 1007-1002-1003-1002
    • affected 1007-1004-1003-1001
    • affected 1008-1001-1003-1002
    • affected 1008-1004-1004-1001
    • affected 1008D-1003D-1004D-1002D
    • affected 1008J-1004J-1004J-1001J
    • affected 1009-1001-1004-1001
    • affected 1009-1002-1005-1003
    • affected 1009-1003-1005-1002
    • affected 1010-1001-1004-1001
    • affected 1010-1001-1004-1002
    • affected 1010-1003-1005-1002
    • affected 1010-1003-1006-1003
    • affected 1010-1003-1006-1004
    • affected 1010-1004-1007-1001
    • and 146 more

References (5)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-34053 badge
[![CVE-2025-34053](https://trackcve.app/badge/CVE-2025-34053.svg)](https://trackcve.app/cve/CVE-2025-34053)

Record last updated .