Skip to main content
VulnerabilityPublished Updated

CVE-2026-105141: topoteretes cognee · Hard-coded Credentials

Affects topoteretes cogneeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.3Medium
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
topoteretescogneeAffected
  • 1.5.0 – 1.5.4
5 affected builds
Fixed in–
GitHubtopoteretes/cogneepkg:github/topoteretes/cogneeOther threatsAffected
  • 1.5.0 – 1.5.4
5 affected builds
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:topoteretes:cognee:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade topoteretes cognee to version 1.6.0 or later to remediate this vulnerability. This upgrade includes the official fix patch fa65fc0cd86cdba48d19aa76e36be862be982f5d. No additional mitigation steps are indicated.

Description

A hard-coded credentials vulnerability exists in topoteretes cognee versions 1.5.0 through 1.5.4 in the JWT Signing Key Handler component. The flaw is due to manipulation of the FASTAPI_USERS_JWT_SECRET argument in the get_user_id_by_email function, allowing remote attackers to exploit hard-coded credentials. Upgrading to version 1.6.0 addresses this issue.

References

Community reviews

Loading reviews…