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.
Published: 2026-09-04
Score: 7.1 High
EPSS: < 1% Very Low
KEV: No
Impact: Sensitive Data Exposure of API keys via tool endpoints
Action: Patch ASAP
AI Analysis

Impact

Onyx 4.6.6 allows any authenticated user to read custom tool credentials that are stored in custom_headers. By accessing GET /tool or GET /tool/{tool_id} endpoints, an attacker can retrieve plaintext authorization headers, including third‑party API keys. These keys can then be used to authenticate directly with upstream services, enabling unauthorized access or data exfiltration.

Affected Systems

The vulnerability impacts the Onyx application produced by onyx-dot-app. Version 4.6.6 is affected; any instance of that exact version running without a newer patched release is at risk.

Risk and Exploitability

With a CVSS score of 7.1, the vulnerability is considered a medium severity risk. EPSS data is not available, so the current likelihood of exploitation is unknown. The vulnerability is not listed in the CISA KEV catalog. Attackers need only authenticated access to the host to trigger the disclosure; no special privileges beyond standard authentication are required. The straightforward HTTP request path makes the exploit trivial for anyone who can log in, so the risk is real and actionable.

Generated by OpenCVE AI on September 4, 2026 at 15:38 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade to the latest Onyx release that includes the fix for the custom‑header disclosure.
  • Restrict access to the "/tool" and "/tool/{tool_id}" endpoints so that only administrators or privileged users can retrieve tool configurations.
  • Immediately rotate all API keys that may have been exposed through custom_headers and revoke any tokens that could have been compromised.
  • Verify that the system’s firewall or network segmentation rules allow only trusted hosts to communicate with the Onyx API endpoints and block any unauthorized outbound connections.

Generated by OpenCVE AI on September 4, 2026 at 15:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 04 Sep 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 04 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
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.
Title Onyx 4.6.6 Custom Tool Secret Header Disclosure via Tool Endpoints
First Time appeared Onyx
Onyx onyx
Weaknesses CWE-522
CPEs cpe:2.3:a:onyx:onyx:*:*:*:*:*:*:*:*
Vendors & Products Onyx
Onyx onyx
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-09-04T14:55:15.464Z

Reserved: 2026-09-04T13:51:53.585Z

Link: CVE-2026-85700

cve-icon Vulnrichment

Updated: 2026-09-04T14:53:27.543Z

cve-icon NVD

Status : Deferred

Published: 2026-09-04T15:17:49.110

Modified: 2026-09-23T17:17:45.033

Link: CVE-2026-85700

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-04T20:45:17Z

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials