Bug 2547878

Summary: CVE-2026-106550 boost: convict: Denial of Service via prototype pollution in config.set() [fedora-all]
Product: [Fedora] Fedora Reporter: Ganesh <gnaik>
Component: boostAssignee: Jonathan Wakely <jwakely>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: rawhideCC: denis.arnaud_fedora, jwakely, laurent.rineau__fedora, mcermak, ppalka
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["bc33a0b6-0ea4-413a-90d9-f57676dc43b9"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-10-08 09:33:23 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: 2547143    

Description Ganesh 2026-10-08 09:23:19 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.

Mozilla's Node-convict (version 6.2.2 and later) is vulnerable to a Denial of Service vulnerability caused by incomplete prototype‑pollution protections in config.set(). An attacker controlling the configuration key can write arbitrary properties to constructor.<key>, which walk() resolves to the global Object function. This allows overwriting core JavaScript methods such as Object.assign, leading to persistent process-wide failures and requiring a restart. The issue bypasses existing filters that only block constructor.prototype.* and __proto__.*. Exploitation requires an endpoint that forwards attacker-controlled keys into config.set().

Comment 1 Jonathan Wakely 2026-10-08 09:32:28 UTC
Please stop filing these for boost. Please.

Comment 2 Jonathan Wakely 2026-10-08 09:33:23 UTC
As I have said repeatedly:

The CVE does not affect Boost. The Node 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."