CYBERSECURITYTRACKER
Permanent story citation

Brotli CVE-2026-111497 and git-remote-https

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 11355

As cited

Copy frozen at (site build).

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

The Brotli vulnerability CVE-2026-111497 affects git-remote-https when libcurl is compiled with Brotli support, a common configuration in most Linux distributions. Developers scanning for vulnerable applications should check for both CURLOPT_ENCODING and CURLOPT_ACCEPT_ENCODING options, as older code may still reference the former alias.

Why it matters: Git and libcurl users need to identify vulnerable versions of git-remote-https on their systems and verify their libcurl build configuration, as this affects HTTPS remote operations across development environments.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

CVE-2026-111497 affects git-remote-https when libcurl is compiled with Brotli compression support, a configuration common in most Linux distributions. Practitioners scanning for vulnerable libcurl installations should also check for the deprecated CURLOPT_ENCODING option, which is an alias for CURLOPT_ACCEPT_ENCODING and may appear in legacy code.

Why it matters: Developers and system administrators relying on Git HTTPS operations face potential compromise if libcurl with Brotli is in use; comprehensive vulnerability scans must account for both current and legacy option names to identify exposure.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

Git's HTTPS remote functionality is vulnerable to CVE-2026-111497 when libcurl is compiled with Brotli support, a configuration common in most Linux distributions. Applications using libcurl should be scanned for both CURLOPT_ENCODING and CURLOPT_ACCEPT_ENCODING options, as older code may still reference the deprecated alias.

Why it matters: DevOps and platform teams using Git over HTTPS need to audit libcurl builds for Brotli support and check for the vulnerable encoding options to identify exposure in their infrastructure.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

Git's HTTPS remote functionality is vulnerable to CVE-2026-111497 when libcurl is compiled with Brotli support, a configuration common in most Linux distributions. Applications using libcurl should be scanned for both CURLOPT_ENCODING and CURLOPT_ACCEPT_ENCODING options, as older code may still reference the deprecated alias.

Why it matters: DevOps and platform teams using Git over HTTPS need to audit libcurl builds for Brotli support and check for the vulnerable encoding options to identify exposure in their infrastructure.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

CVE-2026-111497 affects git-remote-https when libcurl is built with brotli support, which is common across Linux distributions. Applications using libcurl with CURLOPT_ENCODING or its alias CURLOPT_ACCEPT_ENCODING may also be vulnerable to this issue.

Why it matters: Practitioners managing systems with git HTTPS remotes and brotli-enabled libcurl installations should inventory affected deployments and prioritize patching, as this critical vulnerability (CVSS 9.2) is tracked on the Known Exploited Vulnerabilities (KEV) list.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

CVE-2026-111497 affects git-remote-https when libcurl is built with brotli support, which is common across Linux distributions. Applications using libcurl with CURLOPT_ENCODING or its alias CURLOPT_ACCEPT_ENCODING may also be vulnerable to this issue.

Why it matters: Practitioners managing systems with git HTTPS remotes and brotli-enabled libcurl installations should inventory affected deployments and prioritize patching, as this critical vulnerability (CVSS 9.2) is tracked on the Known Exploited Vulnerabilities (KEV) list.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

CVE-2026-111497 affects git-remote-https when libcurl is built with brotli support, which is common across Linux distributions. Applications using libcurl with CURLOPT_ENCODING or its alias CURLOPT_ACCEPT_ENCODING may also be vulnerable to this issue.

Why it matters: Practitioners managing systems with git HTTPS remotes and brotli-enabled libcurl installations should inventory affected deployments and prioritize patching, as this critical vulnerability (CVSS 9.2) is tracked on the Known Exploited Vulnerabilities (KEV) list.

Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Brotli CVE-2026-111497 and git-remote-https

CVE-2026-111497 affects git-remote-https when libcurl is built with brotli support, which is common across Linux distributions. Applications using libcurl with CURLOPT_ENCODING or its alias CURLOPT_ACCEPT_ENCODING may also be vulnerable to this issue.

Why it matters: Practitioners managing systems with git HTTPS remotes and brotli-enabled libcurl installations should inventory affected deployments and prioritize patching, as this critical vulnerability (CVSS 9.2) is tracked on the Known Exploited Vulnerabilities (KEV) list.

VendorsGoogleLinuxWordPress
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary