CVE-2026-85700
Description
Onyx 4.6.6 fails to properly restrict access to custom tool credentials stored in custom_headers, allowing any authenticated user to read admin-defined API keys. Attackers with basic authentication can call GET /tool/{tool_id} or GET /tool endpoints to retrieve plaintext authorization headers and third-party API credentials, then use them to directly access upstream APIs.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
References
- https://github.com/onyx-dot-app/onyx
- https://github.com/onyx-dot-app/onyx/blob/v4.6.6/backend/onyx/server/features/tool/api.py
- https://github.com/onyx-dot-app/onyx/blob/v4.6.6/backend/onyx/server/features/tool/models.py
- https://github.com/onyx-dot-app/onyx/issues/13165
- https://www.vulncheck.com/advisories/onyx-4.6.6-custom-tool-secret-header-disclosure-via-tool-endpoints
CWEs
CWE-522
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.