Improper AuthenticationWeakness · CWE-287

CVE-2026-0629

HIGH · 8.7 CVSS v4.0 Published 2026-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Authentication bypass in the password recovery feature of the local web interface across multiple VIGI camera models allows an attacker on the LAN to reset the admin password without verification by manipulating client-side state. Attackers can gain full administrative access to the device, compromising configuration and network security.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authentication bypass in the password recovery feature of the local web interface allows an attacker on the LAN to reset the admin password without verification by manipulating client-side state, granting full administrative access to the device.

MitigationIsolate affected devices on a restricted network segment and monitor for unauthorized access attempts; apply vendor firmware updates when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the device has a web-based management interface
    Check for accessible HTTP/HTTPS services on the local network that serve a login or administrative portal. Use a port scanner or check network services on common web ports (80, 443, 8080, 8443).
    Affected if A web interface for administrative access is present and reachable on the LAN.
  2. Confirm the password recovery feature exists
    Access the web interface and look for 'forgot password', 'password recovery', or 'reset password' links or endpoints. This may be at paths like /login, /password-reset, /forgot, or similar.
    Affected if A password recovery or password reset functionality is available in the web interface.
  3. Determine if password recovery relies on client-side state
    Inspect the password recovery workflow using browser developer tools or a proxy. Look for hidden fields, cookies, or tokens that could be manipulated on the client side rather than validated server-side.
    Affected if The password reset process accepts or relies on client-side parameters (hidden form fields, cookies, client-generated tokens) without proper server-side verification.
  4. Check for unauthorized admin account changes
    Log into the administrative interface and review user accounts, especially the admin account. Look for unexpected changes to account status, password last-changed dates, or unknown admin-level accounts.
    Affected if The admin password has been changed without authorization, or unauthorized admin accounts exist.
  5. Review access logs for password reset activity
    Examine web server logs, system logs, or any available audit logs for password reset requests, especially from multiple IP addresses or at unexpected times.
    Affected if Password reset or account modification events appear in logs that were not initiated by legitimate administrators.

A user is affected if their device has a LAN-accessible web interface with a password recovery feature that can be bypassed through client-side state manipulation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate affected devices on a restricted network segment and monitor for unauthorized access attempts; apply vendor firmware updates when available.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0629 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0629 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data