CVE-2025-58366
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-05

Last updated on: 2025-09-08

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-05
Last Modified
2025-09-08
Generated
2026-05-06
AI Q&A
2025-09-06
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
insee_fr_lab onyxia-api 4.8.0
insee_fr_lab onyxia-api 4.9.0
insee_fr_lab onyxia-api 4.6.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-522 The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in Onyxia versions 4.6.0 through 4.8.0 causes the Onyxia-API to leak credentials of private helm repositories through the public, unauthenticated /public/catalogs endpoint. Only instances using private helm repositories with configured usernames and passwords are affected. The issue is fixed in version 4.9.0.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized disclosure of private helm repository credentials, potentially allowing attackers to access private repositories and sensitive data or deploy malicious software. This can compromise the security and integrity of your data science environment.


What immediate steps should I take to mitigate this vulnerability?

Upgrade Onyxia to version 4.9.0 or later, as this version fixes the credential leak issue in the /public/catalogs endpoint. Additionally, avoid using private helm repositories with username and password in the catalogs configuration until the upgrade is applied.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart