topoteretes cognee up to 1.5.4 JWT Signing Key get_api_auth_backend.py get_user_id_by_email FASTAPI_USERS_JWT_SECRET hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 1.65- |
Summary
A vulnerability, which was classified as critical, has been found in topoteretes cognee up to 1.5.4. The impacted element is the function get_user_id_by_email of the file cognee/modules/users/authentication/get_api_auth_backend.py of the component JWT Signing Key Handler. This manipulation of the argument FASTAPI_USERS_JWT_SECRET causes hard-coded credentials.
This vulnerability is registered as CVE-2026-105141. Remote exploitation of the attack is possible. No exploit is available.
It is advisable to upgrade the affected component.
Details
A vulnerability has been found in topoteretes cognee up to 1.5.4 and classified as critical. Affected by this vulnerability is the function get_user_id_by_email of the file cognee/modules/users/authentication/get_api_auth_backend.py of the component JWT Signing Key Handler. The manipulation of the argument FASTAPI_USERS_JWT_SECRET with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-105141. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
Upgrading to version 1.6.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch fa65fc0cd86cdba48d19aa76e36be862be982f5d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-92086). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: cognee 1.6.0
Patch: fa65fc0cd86cdba48d19aa76e36be862be982f5d
Timeline
10/03/2026 Advisory disclosed10/03/2026 VulDB entry created
10/04/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 5062
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2026-105141 (🔒)
GCVE (CVE): GCVE-0-2026-105141
GCVE (VulDB): GCVE-100-413365
EUVD: 🔒
Entry
Created: 10/03/2026 16:31Updated: 10/04/2026 11:10
Changes: 10/03/2026 16:31 (61), 10/04/2026 11:10 (1)
Complete: 🔍
Submitter: zhuke
Cache ID: 216::103
Submit
Accepted
- Submit #944531: Cognee 1.4.1 Insecure Default Variable / Hardcoded Secret (by zhuke)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.