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

How to Fix CVE-2026-4673: Path Traversal in Chrome

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

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityNot verified - see advisory
Actively exploited?Not currently listed in CISA KEV
Affected146.0.7680.165 < 146.0.7680.165
Fixed inSee vendor advisory
Type (CWE)CWE-122: Heap buffer overflow

What is CVE-2026-4673?

CVE-2026-4673 is a path traversal flaw in Chrome. The product fails to canonicalize or restrict file paths supplied by a remote caller, so .. sequences or absolute paths reach restricted parts of the filesystem. Vendor description: Heap buffer overflow in WebAudio in Google Chrome prior to 146.0.7680.165 allowed a remote attacker to perform an out of bounds memory write via a crafted HTML page. (Chromium security severity: High)

Why this CVE matters

Path traversal flaws look low-impact on paper but routinely chain into full compromise. An attacker who can read arbitrary files often pulls configuration secrets, session databases, or private keys, and many traversal bugs also allow writes that drop a webshell into the document root.

For deployments of Chrome 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 Chrome'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-4673

  1. Read the vendor advisory in full: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html
  2. Upgrade Chrome to the patched build listed in the vendor advisory.
  3. Back up the configuration (and database, where applicable) before upgrading.
  4. Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
  5. Restart the affected service so the patched binary loads, then verify the new version (see verification section).

Upgrade Google Chrome


# CVE-2026-4673 affects Chrome 146.0.7680.165 < 146.0.7680.165.
# Fixed in 146.0.7680.165. Vendor advisory: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html

# 1. Identify the running version using the vendor-documented command.
#    (Open the product UI -> About, or run the CLI version probe.)

# 2. Stage the patched build named in the advisory.
#    Vendor advisory: https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html

# 3. Apply the upgrade. If the vendor ships a Linux package, pull it via your
#    distribution's package manager:
sudo apt update && sudo apt install --only-upgrade chrome        # Debian / Ubuntu
sudo dnf upgrade chrome                                          # RHEL / Rocky / Alma / Fedora

# 4. Restart the affected service so the new binary loads.
sudo systemctl restart chrome 2>/dev/null || true

# 5. Re-run the version probe and confirm it matches 146.0.7680.165.


# Windows-hosted installs of Chrome: apply via PSWindowsUpdate or the vendor MSI.
Install-Module PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Get-WindowsUpdate -AcceptAll -Install -AutoReboot

Verify the fix landed


# CVE-2026-4673 verification checklist.

# 1. Confirm the running version matches 146.0.7680.165 (replace the version probe with
#    the platform-specific command shown above).

# 2. Re-scan the host with your vulnerability scanner (Nessus, Qualys, Tenable,
#    OpenVAS, Wazuh). The scanner must no longer flag CVE-2026-4673.

# 3. Inspect recent service and kernel logs for crash-loops or rollback events.
journalctl -u <service-name> --since "10 minutes ago"
dmesg --since "10 minutes ago"

# 4. Cross-check the running build against the vendor advisory:
#    https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_23.html

If you cannot patch immediately

Block requests containing ../, ..%2f, or absolute path prefixes at a reverse proxy. Restrict access to the affected endpoint to trusted networks. Apply the patched build as the real fix.

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 unusually long URI paths containing traversal sequences, unexpectedly large responses from the affected endpoint, and outbound requests from the application to internal addresses or cloud-metadata endpoints. Treat any sensitive file the bug could disclose as exposed.

Frequently asked questions

Is CVE-2026-4673 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-4673?

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.

How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for Chrome run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

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.*