⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.7

How to Fix CVE-2026-0629: Authentication Bypass in VIGI InSight Sx45 Series (S245/S345/S445)

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.7 - High
Actively exploited?Not currently listed in CISA KEV
Affected0 < 3.1.0_Build_250820_Rel.57668n, 0 < 3.1.0_Build_250820_Rel.57668n, 0 < 3.1.0_Build_250820_Rel.58873n, 0 < 3.1.0_Build_250820_Rel.58873n, 0 < 3.0.2_Build_250630_Rel.71279n, 0 < 3.0.2_Build_250630_Rel.71279n, and others
Fixed inSee vendor advisory
Type (CWE)CWE-287: Improper Authentication

What is CVE-2026-0629?

CVE-2026-0629 is an authentication bypass in VIGI InSight Sx45 Series (S245/S345/S445). A flaw in the authentication or session-handling logic lets a remote attacker reach administrative functions without valid credentials. In several reported cases this leads directly to remote code execution. Vendor description: 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.

Why this CVE matters

Authentication bypass on a network appliance or admin console is a top-tier target. Once the attacker is past the login, every administrative endpoint becomes available, including the ones that change settings, upload firmware, or run shell commands.

For deployments of VIGI InSight Sx45 Series (S245/S345/S445) that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open VIGI InSight Sx45 Series (S245/S345/S445)'s About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-0629

The fix is to upgrade VIGI InSight Sx45 Series (S245/S345/S445) to one of these patched versions (pick the one matching your release line): 3.1.0_Build_250820_Rel.57668n, 3.1.0_Build_250820_Rel.58873n, 3.0.2_Build_250630_Rel.71279n.

Affected versions confirmed in the CVE record:

Apply the firmware update


<!-- enrich_agent_2:v1 -->
# Affected models + patched firmware (from the vendor advisory):
# - VIGI InSight Sx45 Series (S245/S345/S445): install firmware 3.1.0_Build_250820_Rel.57668n or later
# - VIGI Cx45 Series (C345/C445): install firmware 3.1.0_Build_250820_Rel.57668n or later
# - VIGI InSight Sx55 Series (S355/S455): install firmware 3.1.0_Build_250820_Rel.58873n or later
# - VIGI Cx55 Series (C355/C455): install firmware 3.1.0_Build_250820_Rel.58873n or later
# - VIGI InSight Sx85 Series (S285/S385): install firmware 3.0.2_Build_250630_Rel.71279n or later
# - VIGI Cx85 Series (C385/C485): install firmware 3.0.2_Build_250630_Rel.71279n or later
# - VIGI InSight S655I: install firmware 1.1.1_Build_250625_Rel.64224n or later
# - VIGI InSight Sx45ZI Series (S245ZI/S345ZI/S445ZI): install firmware 1.2.0_Build_250820_Rel.60930n or later
# - VIGI InSight Sx85PI Series (S385PI/S485PI): install firmware 1.2.0_Build_250827_Rel.66817n or later
# - VIGI C340S: install firmware 3.1.0_Build_250625_Rel.65381n or later
# - VIGI C540S / EasyCam C540S: install firmware 3.1.0_Build_250625_Rel.66601n or later
# - VIGI C540V: install firmware 2.1.0_Build_250702_Rel.54300n or later

# 1. Open the device's web admin UI on its LAN address.
#    (Most models default to http://192.168.1.1/ or http://routerlogin.net/.)
#    Sign in with the admin account.

# 2. Navigate to ADVANCED -> Administration -> Firmware Update (or "Router
#    Update"). Click Check. If the device offers an OTA, install it.

# 3. If no OTA is offered, download the patched .img / .chk firmware from the
#    vendor's product page (linked above) and upload it manually via
#    Administration -> Firmware Update -> Browse -> Upload.

# 4. Reboot when prompted, then re-confirm the running firmware version in
#    ADVANCED -> Administration -> Router Information.


<!-- enrich_agent_2:v1 -->
# Optional: pull the device-info page to confirm the running firmware version
# over the LAN (NETGEAR / generic example).
Invoke-WebRequest -Uri "http://routerlogin.net/RST_status.htm" -UseDefaultCredentials |
  Select-String -Pattern "Firmware Version"

Verify the fix worked


<!-- enrich_agent_2:v1 -->
# 1. Confirm the running version matches the fixed-in version from the advisory.
#    Cross-check against the vendor advisory: https://www.tp-link.com/us/support/faq/4906/

# 2. Re-scan with your vulnerability scanner. The scanner should no longer flag
#    this CVE on the patched host.
# Example with Nmap NSE:
nmap -sV --script vuln <target-host>

# 3. Inspect the service / kernel logs for crash-loops or rollback events in
#    the first hour after the upgrade.
journalctl -u <service-name> --since "1 hour ago"
dmesg --since "1 hour ago"

If you cannot patch immediately

Restrict access to the affected administrative interface to trusted internal networks. Disable the vulnerable component if the vendor documents that as an interim option. Patch immediately when feasible.

How to verify the fix worked

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for unexpected administrator accounts in VIGI InSight Sx45 Series (S245/S345/S445), scheduled tasks or cron jobs you did not create, new files in web-accessible directories, and outbound connections to addresses not in your baseline. Suspicious requests to the vulnerable endpoint immediately followed by successful 200-class responses with unusually large bodies are a strong indicator of exploitation.

Frequently asked questions

Is CVE-2026-0629 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Will a WAF or IDS rule fully mitigate CVE-2026-0629?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Do I need to assume compromise if my VIGI InSight Sx45 Series (S245/S345/S445) was internet-facing and unpatched?

For an unauthenticated RCE-class flaw exposed to the public internet during the known exploitation window, yes. Review logs, rotate credentials the process could access, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*