Details
Relationship to recent prototype-pollution work
Same vulnerability class as the existing public hardening, just at
sub-field granularity:
- GHSA-q8qp-cvcw-x6jj / PR #10779 —
mergeConfigdirect-key reads. Fixed in v1.15.2. - PR #10761 —
mergeDirectKeysin→hasOwnProp. Fixed in v1.15.x. - PR #10833 — proxy
auth.username/passwordsub-fields. Fixed post-1.16.1. - PR #7413 —
formDataToJSONdefense-in-depth. Fixed post-1.16.1. - PR #10901 —
socketPathguard. Merged 2026-05-24. - PR #10922 (OPEN) —
params/paramsSerializerown()guard. Proposed; not merged.
This report adds: regular-request auth.username / auth.password
sub-field reads in both the http adapter (lines 737–740) and
resolveConfig.js (line 68).
Reporter notes
- Reported as part of a small peer-review bundle of runtime security findings. The bundle's public tracking entry (without the working exploit chain) is at `georgian-io/package-runtime-security-findings/advisories/AXIOS-002-prototype-pollution-config-fields.md`.
- I'm happy to submit the patch as a PR if that helps. Or, if you'd prefer to fold this into open PR #10922 (whose author is actively responding to comments), please let me know and I'll coordinate.
- Threat model honesty: this is amplifier framing — exploitation requires a separate prototype-pollution primitive elsewhere in the host process. That's how the existing GHSA-q8qp-cvcw-x6jj and PR #10833 were framed too, so the precedent for "in-scope as a hardening fix" is established.
</details>