Skip to main content
VulnerabilityPublished Updated

CVE-2025-58366: InseeFrLab onyxia · Insufficiently Protected Credentials

Affects InseeFrLab onyxiaSource CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical · fixed in 4.9.0 : patch InseeFrLab onyxia as a priority.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.9.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Immediate upgrade of Onyxia to version 4.9.0 or later, where the vulnerability is patched, is the most effective mitigation.
  2. Until the upgrade is applied, restrict access to the /public/catalogs endpoint via network-level controls such as firewalls or API gateways to limit exposure to trusted users only.
  3. Review and rotate all credentials for private Helm repositories that were potentially exposed through the vulnerable endpoint to prevent unauthorized access.
  4. Implement strict access controls and monitoring on private Helm repositories to detect any unauthorized access or anomalous activity.
  5. Employ Kubernetes network policies to limit external access to Onyxia APIs and endpoints.
  6. Conduct an audit of all Onyxia deployments to identify instances using private Helm repositories and verify they are updated or mitigated accordingly.
  7. Educate DevOps and security teams about the risks of exposing sensitive credentials in publicly accessible endpoints and enforce secure configuration management practices.

Description

Onyxia is a data science environment for kubernetes. In versions 4.6.0 through 4.8.0, Onyxia-API leaked the credentials of private helm repositories in the public (unauthenticated) /public/catalogs endpoint.vOnly instances using private helm repositories (i.e setting username & password in the catalogs configuration) are affected. This is fixed in version 4.9.0.

References

Community reviews

Loading reviews…