Bug 2510268

Summary: CVE-2026-67316 boost: axios: Prototype Pollution allows unauthorized data transmission and network redirection [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: low Docs Contact:
Priority: low    
Version: rawhideCC: denis.arnaud_fedora, jwakely, laurent.rineau__fedora, mcermak, ppalka
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["aadd2b7c-a7c3-4b86-82a3-a2486ee4c190"]}
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-08-03 12:52:02 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: 2510009    

Description Ganesh 2026-08-03 04:07:24 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.

axios is vulnerable to read-side prototype-pollution gadgets that can alter request construction when Object.prototype has already been polluted by a separate vulnerability or dependency. In the bodyless method aliases (axios.get(), axios.delete(), axios.head(), axios.options()), inherited data is read via (config || {}).data before config normalization, causing an attacker-controlled body to be sent on requests that did not set one. Additional low-level paths, only reachable when calling exported adapters/helpers (e.g. lib/adapters/http.js, unsafe/helpers/resolveConfig.js) directly with plain configs and no own proxy or paramsSerializer, can inherit polluted proxy values (routing requests through an attacker-controlled proxy) or paramsSerializer values (attacker-controlled URL serialization). These low-level gadgets do not reproduce through normal high-level axios calls on 1.15.2+. The issue is fixed in axios 1.18.0 and 0.33.0.

Comment 1 Jonathan Wakely 2026-08-03 12:52:02 UTC
As I have said repeatedly:

The CVE does not affect Boost. The Axios module is only used to generate HTML files during preparation of the release tarball, and is not used during the RPM build and is 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."

Comment 2 Jonathan Wakely 2026-08-03 12:53:24 UTC
ProdSec: Is it possible to get boost excluded from these axios CVE bug reports?