PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-105141 topoteretes CVE debrief

A security flaw has been discovered in topoteretes cognee up to 1.5.4. The affected 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. The manipulation of the argument FASTAPI_USERS_JWT_SECRET results in hard-coded credentials. The attack may be launched remotely. Upgrading to version 1.6.0 is sufficient to fix this issue. The patch is identified as fa65fc0cd86cdba48d19aa76e36be862be982f5d. Upgrading the affected component is advised.

Vendor
topoteretes
Product
cognee
CVSS
MEDIUM 5.3
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-04
Original CVE updated
2026-10-04
Advisory published
2026-10-04
Advisory updated
2026-10-04

Who should care

Defenders responsible for topoteretes cognee deployments should assess exposure and verify the presence of the patched version. They should review the configuration of the FASTAPI_USERS_JWT_SECRET argument to prevent unauthorized access. Security teams and vulnerability management teams should prioritize this issue based on the medium severity and remote attack vector.

Why it matters

CVE-2026-105141 is a medium-severity vulnerability in topoteretes cognee that allows remote attacks via hard-coded credentials. Defenders should prioritize verifying the presence of the patched version 1.6.0 and review the configuration of the FASTAPI_USERS_JWT_SECRET argument.

  • Verify the configuration of the FASTAPI_USERS_JWT_SECRET argument to prevent unauthorized access
  • Upgrade to version 1.6.0 to apply the patch
  • Review and restrict access to the affected component

Technical summary

The vulnerability is located in the get_user_id_by_email function of the cognee/modules/users/authentication/get_api_auth_backend.py file. The FASTAPI_USERS_JWT_SECRET argument is not properly secured, leading to hard-coded credentials. This allows remote attacks via hard-coded credentials. Upgrading to version 1.6.0 is sufficient to fix this issue. The patch is identified as fa65fc0cd86cdba48d19aa76e36be862be982f5d. Defenders should prioritize verifying the presence of the patched version 1.6.0 and review the configuration of the FASTAPI_USERS_JWT_SECRET argument.

Defensive priority

Defenders should prioritize verifying the presence of the patched version 1.6.0 and review the configuration of the FASTAPI_USERS_JWT_SECRET argument.

Recommended defensive actions

  • Verify the presence of the patched version 1.6.0
  • Review the configuration of the FASTAPI_USERS_JWT_SECRET argument
  • Upgrade the affected component
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source references provide information on the vulnerability, patch, and affected version. The vulnerability is confirmed in topoteretes cognee up to 1.5.4. Defenders should verify the presence of the patched version 1.6.0 and review the configuration of the FASTAPI_USERS_JWT_SECRET argument. Evidence is limited to public CVE details and supplied source references. Further verification is recommended.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-105141 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-105141

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-105141 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-105141

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.