Bug 2536995

Summary:	CVE-2026-89011 boost: isomorphic-git: Information disclosure via prototype pollution in getRemoteInfo function. [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Marian Rehak <mrehak>
Component:	boost	Assignee:	Jonathan Wakely <jwakely>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	high
Version:	rawhide	CC:	denis.arnaud_fedora, jwakely, laurent.rineau__fedora, mcermak, ppalka
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["618fd367-858b-442c-a34d-c853d84b4ca8"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-09-18 12:43:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2531620

Description Marian Rehak 2026-09-18 12:32:18 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

isomorphic-git before 1.42.0 contains a prototype pollution vulnerability in the getRemoteInfo function that allows a malicious Git server operator to pollute Object.prototype by advertising crafted ref names containing '__proto__' path segments during ref negotiation. Attackers controlling a Git server can advertise a specially crafted ref such as '__proto__/corsProxy' to reroute all subsequent network operations through an attacker-controlled proxy, causing isomorphic-git to invoke the victim's onAuth callback and transmit credentials to the attacker when the victim calls getRemoteInfo with an attacker-supplied URL.

Comment 1 Jonathan Wakely 2026-09-18 12:43:15 UTC

say-the-line-bart.jpg


The CVE does not affect Boost. The nodejs modules are only used to generate HTML files during preparation of the release tarball, and are not used during the RPM build and are not part of the installed RPMs.

I checked this with upstream and was told "The npm packages are only required at doc build time, so it makes
sense to not include them in the release tarball."
https://lists.boost.org/archives/list/boost@lists.boost.org/thread/APKJIASXU2DLQMGYIQR4JOMJE5CB56KB/

The Boost 1.92.0 release will not include those files in the release tarball at all, due to https://github.com/boostorg/release-tools/pull/111 which was already changed in March. That PR says "Remove "doc/node_modules" from libraries after the build. Since that directory adds extra MBs, and isn't needed."