Common Weakness Enumeration

CWE-613

Weakness Prohibited

DEPRECATED: Insufficient Session Expiration

Abstraction: Base · Status: Deprecated

This entry has been deprecated because it was insufficiently clear. Consider CWE-1462 and its descendants.

Mapping guidance

This CWE has been deprecated.

See description and name for possible suggestions of other CWEs to consider.

Relationships and members
ChildOf: CWE-672 · View CWE-1003
Notes

Maintenance · CWE 5.0 · 2026-10-27

This CWE entry has been deprecated. For many years, the intention and usage of this CWE entry has evolved to include many notions of "sessions" that are not specific to the web. Instead of expanding the scope of this entry, it was split into multiple separate entries. The original WASC-47 entry [REF-1520] includes considerations forcing re-authentication for "inactivity" (expiring sessions after a period of inactivity) versus "absolute" (a fixed expiration time), with a goal to "keep the lifespan of a session ID as short as possible." However, this CWE was also used for situations in which a session is not fully invalidated or terminated upon logout, which is a different weakness than the original intention for this entry. There is also evidence that this CWE entry was used for session fixation (CWE-384).

Content history
Submission: WASC · 2007-05-07 · CWE Draft 6
Modification: Sean Eidemiller · Cigital · 2008-07-01 · CWE 1.0

added/updated demonstrative examples

Modification: Eric Dalci · Cigital · 2008-07-01 · CWE 1.0

updated Potential_Mitigations, Time_of_Introduction

Modification: CWE Content Team · MITRE · 2008-09-08 · CWE 1.0

updated Relationships, Other_Notes, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2009-03-10 · CWE 1.3

updated Relationships

Modification: CWE Content Team · MITRE · 2010-02-16 · CWE 1.8

updated Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2010-09-27 · CWE 1.10

updated Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2011-06-01 · CWE 1.13

updated Common_Consequences

Modification: CWE Content Team · MITRE · 2012-05-11 · CWE 2.2

updated Relationships

Modification: CWE Content Team · MITRE · 2012-10-30 · CWE 2.3

updated Potential_Mitigations

Modification: CWE Content Team · MITRE · 2014-06-23 · CWE 2.7

updated Relationships

Modification: CWE Content Team · MITRE · 2014-07-30 · CWE 2.8

updated Relationships

Modification: CWE Content Team · MITRE · 2017-11-08 · CWE 3.0

updated Modes_of_Introduction, Relationships

Modification: CWE Content Team · MITRE · 2018-03-27 · CWE 3.1

updated Relationships

Modification: CWE Content Team · MITRE · 2019-06-20 · CWE 3.3

updated Relationships

Modification: CWE Content Team · MITRE · 2020-02-24 · CWE 4.0

updated Relationships

Modification: CWE Content Team · MITRE · 2021-10-28 · CWE 4.6

updated Relationships

Modification: CWE Content Team · MITRE · 2023-04-27 · CWE 4.11

updated Detection_Factors, Relationships

Modification: CWE Content Team · MITRE · 2023-06-29 · CWE 4.12

updated Mapping_Notes

Modification: CWE Content Team · MITRE · 2025-12-11 · CWE 4.19

updated Applicable_Platforms, Relationships, Weakness_Ordinalities

Modification: CWE Content Team · MITRE · 2026-04-30 · CWE 4.20

updated Maintenance_Notes, Mapping_Notes, Observed_Examples, References

Modification: CWE Content Team · MITRE · 2026-10-28 · CWE 5.0

updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Detection_Factors, Maintenance_Notes, Mapping_Notes, Modes_of_Introduction, Name, Observed_Examples, Other_Notes, Potential_Mitigations, References, Relationships, Taxonomy_Mappings, Time_of_Introduction, Type, Weakness_Ordinalities

1193 vulnerabilities reference this CWE, most recent first.

CVE-2026-133652 (GCVE-0-2026-133652)

Vulnerability from cvelistv5 – Published: 2026-11-20 10:24 – Updated: 2026-11-20 16:39
VLAI
Title
Flowintel Session Identifiers Not Bound to Credentials Allow Persistent Access After Password Change
Summary
Flowintel , contained a session management vulnerability in its browser authentication mechanism. The session identifier used a bare numeric user ID rather than a credential-bound token, resulting in several related weaknesses: - Remembered logins (remember-me cookies) remained valid after a user changed their password, allowing an attacker holding a previously issued cookie to retain access indefinitely. - Server-side session identifiers were not rotated upon login (local, SSO, or remembered), enabling session fixation. - Self-service email and password changes did not require verification of the current password, permitting an attacker with an active session to modify account credentials without knowledge of the existing password. - Administrator-initiated password resets did not revoke other browser sessions, invalidate remembered logins, or rotate the affected user's API key. An attacker who obtained a valid session or remember-me cookie (e.g., through XSS, network interception, or cookie theft) could maintain unauthorized access even after the legitimate user changed their password. Additionally, an attacker with any valid session could change the account's email address or password without knowing the current credentials, effectively taking over the account. Affected versions: Flowintel prior to 4.1.0.
SSVC
Exploitation: none Automatable: yes Technical Impact: total
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-20 10:20 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 16:23 UTC
CWE
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version
flowintel flowintel Affected: 0 , < 4.1.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-20 10:20
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch cc71c944b258…
Confidence
medium
Commit Subject Patch SHA-256
a7f025ecfdf6 fix: [security] Revoke browser sessions when credentials cc71c944b258…
Fix summary

The fix binds browser session identifiers to the account's current credentials using an HMAC-SHA256 token derived from the user ID, auth provider, creation date, and password hash. All login paths (local, SSO, remembered) now rotate the server-side session ID. Self-service email and password changes require the current password. A self-service password change refreshes the owner's session while revoking all other browser sessions and remembered logins. Administrator password resets additionally rotate the user's API key. Legacy bare-ID session identifiers are rejected by the user loader, and session housekeeping code is updated to parse the new format safely.

Patch summary

Added a session_token() method to the User model that computes an HMAC-SHA256 over the user ID, auth provider, creation date, and password hash; get_id() now returns a composite identifier of the form 'id:token'. The load_user callback validates the new format and rejects legacy bare IDs using constant-time comparison. A _start_user_session() helper clears the session, logs out, logs in, and regenerates the session ID; it replaces all prior login_user() call sites across local, Entra ID, Keycloak, and SimpleSAML login flows. A user_loaded_from_cookie signal handler triggers session ID rotation on remembered-login restoration. A current_password field and validator were added to the EditUserForm, requiring the existing password for email or password changes on local accounts. The admin_edit_user_core function now regenerates the API key on password reset. The _invalidate_user_sessions and list_active_user_sessions helpers were updated to parse the new identifier format via a session_user_id() helper. Test logi

CVSS rationale

AV:N: The vulnerability is in a web application accessible over the network. AC:L: Exploitation requires only a valid session or remember-me cookie and knowledge of the user ID (often sequential); no special race conditions or complex timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker needs a low-privilege valid session (any authenticated user) or a stolen remember-me cookie; no administrative access is required. UI:N: The session persists without any further user interaction; the victim does not need to perform any action for the attacker to retain access. VC:L: An attacker with a persistent session can view data accessible to the compromised account, but this is a secondary effect. VI:H: The attacker can change the account's email and password without knowing the current password, resulting in full account takeover and persistent unauthorized access. VA:H: The legitimate user's access is undermined by the attacker's persistent session, and the attacker can maintain indefinite access. SC/SI/SA:N: The impact is confined to the Flowintel application itself; no other components are directly affected.

Weakness rationale
  • CWE-613 The primary weakness is that browser sessions and remembered logins were not invalidated when credentials changed. The session identifier (a bare user ID) did not incorporate any credential state, so sessions outlived password changes and could be restored after deletion. This is a textbook insufficient session expiration issue.
  • CWE-384 Server-side session IDs were not rotated upon any login event (local, SSO, or remembered). An attacker could fix a known session ID before the victim authenticated and retain access afterward. The patch adds session ID regeneration on all authentication transitions.
  • CWE-287 The session identifier was a bare, predictable numeric user ID with no cryptographic binding to the account's credentials. This allowed session identifiers to be trivially guessed or forged by anyone who knew a user's ID, constituting improper authentication. The uncertainty is that the primary impact is session persistence rather than direct forgery, but the root cause is the lack of credential binding in the authentication token.
Attack pattern rationale
  • CAPEC-18 The session identifier was a bare sequential user ID, making it trivially predictable. An attacker who knew or guessed a user's ID could construct a valid session identifier without any cryptographic secret. This is the closest CAPEC to the root cause: the session token lacked unpredictability and was not bound to any secret. The uncertainty is that the patch's primary fix is credential binding and session rotation rather than increasing token entropy, but the predictability of the bare ID is the enabling condition for the session persistence and fixation issues.
  • CAPEC-60 An attacker who obtained a valid session or remember-me cookie (via XSS, network sniffing, or other means) could maintain access after the legitimate user changed their password, effectively hijacking the session indefinitely. The lack of session revocation on credential change and the absence of session ID rotation made this hijack persistent. This is a secondary mapping; CAPEC-18 is preferred as the root cause, but CAPEC-60 better describes the attacker's end-to-end goal.
Assumptions to verify
  • The affected version range is inferred from the explicit context (affected_version '0', fixed_version '4.1.0'); the patch itself does not enumerate specific prior versions.
  • CVSS PR:L assumes the attacker already holds a valid session or remember-me cookie; if the attacker must first obtain one via a separate vulnerability, the effective privilege requirement may be higher.
  • CVSS VC:L is assigned because a persistent session grants data access, but the primary impact is integrity (account takeover) rather than direct data exfiltration.
  • CAPEC-18 (Session Prediction) is selected as the closest match because the bare user ID is the root cause of the predictability; however, the patch's primary remediation is credential binding and session rotation rather than increasing token entropy, so the mapping is approximate.
  • The patch does not specify whether the vulnerability was reported through a coordinated disclosure process or a public channel; elhoim is credited as reporter based solely on the commit message.
  • The SSVC 'automatable: yes' assessment assumes the attacker can script session reuse or credential modification via HTTP requests; no evidence of an existing automated exploit is present.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 medium 6
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-02 13:43 UTC Fix developed Corrective change authored (a7f025ecfdf60dc0ea3438c79b21a8edc2449836): fix: [security] Revoke browser sessions when credentials https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch
  2. 2026-11-20 10:19 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133652",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:23:44.790740Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T16:39:25.381Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/account/account.py",
            "app/account/form.py",
            "app/admin/admin_core.py",
            "app/db_class/db.py",
            "app/chatbot/chatbot_core.py"
          ],
          "product": "flowintel",
          "programFiles": [],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThan": "4.1.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "elhoim"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Flowintel , contained a session management vulnerability in its browser authentication mechanism. The session identifier used a bare numeric user ID rather than a credential-bound token, resulting in several related weaknesses:\n\n- Remembered logins (remember-me cookies) remained valid after a user changed their password, allowing an attacker holding a previously issued cookie to retain access indefinitely.\n- Server-side session identifiers were not rotated upon login (local, SSO, or remembered), enabling session fixation.\n- Self-service email and password changes did not require verification of the current password, permitting an attacker with an active session to modify account credentials without knowledge of the existing password.\n- Administrator-initiated password resets did not revoke other browser sessions, invalidate remembered logins, or rotate the affected user\u0027s API key.\n\nAn attacker who obtained a valid session or remember-me cookie (e.g., through XSS, network interception, or cookie theft) could maintain unauthorized access even after the legitimate user changed their password. Additionally, an attacker with any valid session could change the account\u0027s email address or password without knowing the current credentials, effectively taking over the account.\n\nAffected versions: Flowintel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-18",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-18 Session Prediction"
            }
          ]
        },
        {
          "capecId": "CAPEC-60",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-60 Session Hijacking"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.2,
            "baseSeverity": "HIGH",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "HIGH",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "HIGH",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "total"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-20T10:20:10Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613 Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-384",
              "description": "CWE-384 Session Fixation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287 Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T10:24:38.906Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The fix binds browser session identifiers to the account\u0027s current credentials using an HMAC-SHA256 token derived from the user ID, auth provider, creation date, and password hash. All login paths (local, SSO, remembered) now rotate the server-side session ID. Self-service email and password changes require the current password. A self-service password change refreshes the owner\u0027s session while revoking all other browser sessions and remembered logins. Administrator password resets additionally rotate the user\u0027s API key. Legacy bare-ID session identifiers are rejected by the user loader, and session housekeeping code is updated to parse the new format safely."
        }
      ],
      "title": "Flowintel Session Identifiers Not Bound to Credentials Allow Persistent Access After Password Change",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected version range is inferred from the explicit context (affected_version \u00270\u0027, fixed_version \u00274.1.0\u0027); the patch itself does not enumerate specific prior versions.",
                  "CVSS PR:L assumes the attacker already holds a valid session or remember-me cookie; if the attacker must first obtain one via a separate vulnerability, the effective privilege requirement may be higher.",
                  "CVSS VC:L is assigned because a persistent session grants data access, but the primary impact is integrity (account takeover) rather than direct data exfiltration.",
                  "CAPEC-18 (Session Prediction) is selected as the closest match because the bare user ID is the root cause of the predictability; however, the patch\u0027s primary remediation is credential binding and session rotation rather than increasing token entropy, so the mapping is approximate.",
                  "The patch does not specify whether the vulnerability was reported through a coordinated disclosure process or a public channel; elhoim is credited as reporter based solely on the commit message.",
                  "The SSVC \u0027automatable: yes\u0027 assessment assumes the attacker can script session reuse or credential modification via HTTP requests; no evidence of an existing automated exploit is present."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-18",
                    "rationale": "The session identifier was a bare sequential user ID, making it trivially predictable. An attacker who knew or guessed a user\u0027s ID could construct a valid session identifier without any cryptographic secret. This is the closest CAPEC to the root cause: the session token lacked unpredictability and was not bound to any secret. The uncertainty is that the patch\u0027s primary fix is credential binding and session rotation rather than increasing token entropy, but the predictability of the bare ID is the enabling condition for the session persistence and fixation issues."
                  },
                  {
                    "capecId": "CAPEC-60",
                    "rationale": "An attacker who obtained a valid session or remember-me cookie (via XSS, network sniffing, or other means) could maintain access after the legitimate user changed their password, effectively hijacking the session indefinitely. The lack of session revocation on credential change and the absence of session ID rotation made this hijack persistent. This is a secondary mapping; CAPEC-18 is preferred as the root cause, but CAPEC-60 better describes the attacker\u0027s end-to-end goal."
                  }
                ],
                "commit": "a7f025ecfdf60dc0ea3438c79b21a8edc2449836",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "elhoim"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N: The vulnerability is in a web application accessible over the network. AC:L: Exploitation requires only a valid session or remember-me cookie and knowledge of the user ID (often sequential); no special race conditions or complex timing are needed. AT:N: No manipulation of the attack target is required. PR:L: The attacker needs a low-privilege valid session (any authenticated user) or a stolen remember-me cookie; no administrative access is required. UI:N: The session persists without any further user interaction; the victim does not need to perform any action for the attacker to retain access. VC:L: An attacker with a persistent session can view data accessible to the compromised account, but this is a secondary effect. VI:H: The attacker can change the account\u0027s email and password without knowing the current password, resulting in full account takeover and persistent unauthorized access. VA:H: The legitimate user\u0027s access is undermined by the attacker\u0027s persistent session, and the attacker can maintain indefinite access. SC/SI/SA:N: The impact is confined to the Flowintel application itself; no other components are directly affected.",
                "fixSummary": "The fix binds browser session identifiers to the account\u0027s current credentials using an HMAC-SHA256 token derived from the user ID, auth provider, creation date, and password hash. All login paths (local, SSO, remembered) now rotate the server-side session ID. Self-service email and password changes require the current password. A self-service password change refreshes the owner\u0027s session while revoking all other browser sessions and remembered logins. Administrator password resets additionally rotate the user\u0027s API key. Legacy bare-ID session identifiers are rejected by the user loader, and session housekeeping code is updated to parse the new format safely.",
                "generatedAt": "2026-11-20T10:20:10.629438Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 6,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "cc71c944b258cbbb2691a3c344be8ab238c168c273adbfd4caa4f051a1bf0315",
                "patchSummary": "Added a session_token() method to the User model that computes an HMAC-SHA256 over the user ID, auth provider, creation date, and password hash; get_id() now returns a composite identifier of the form \u0027id:token\u0027. The load_user callback validates the new format and rejects legacy bare IDs using constant-time comparison. A _start_user_session() helper clears the session, logs out, logs in, and regenerates the session ID; it replaces all prior login_user() call sites across local, Entra ID, Keycloak, and SimpleSAML login flows. A user_loaded_from_cookie signal handler triggers session ID rotation on remembered-login restoration. A current_password field and validator were added to the EditUserForm, requiring the existing password for email or password changes on local accounts. The admin_edit_user_core function now regenerates the API key on password reset. The _invalidate_user_sessions and list_active_user_sessions helpers were updated to parse the new identifier format via a session_user_id() helper. Test logi",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "a7f025ecfdf60dc0ea3438c79b21a8edc2449836",
                    "date": "Mon, 2 Nov 2026 14:43:10 +0100",
                    "patchSha256": "cc71c944b258cbbb2691a3c344be8ab238c168c273adbfd4caa4f051a1bf0315",
                    "retrievedAt": "2026-11-20T10:19:26.228826Z",
                    "source": "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch",
                    "subject": "fix: [security] Revoke browser sessions when credentials"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "total"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T10:20:10Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Revoke browser sessions when credentials",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-613",
                    "rationale": "The primary weakness is that browser sessions and remembered logins were not invalidated when credentials changed. The session identifier (a bare user ID) did not incorporate any credential state, so sessions outlived password changes and could be restored after deletion. This is a textbook insufficient session expiration issue."
                  },
                  {
                    "cweId": "CWE-384",
                    "rationale": "Server-side session IDs were not rotated upon any login event (local, SSO, or remembered). An attacker could fix a known session ID before the victim authenticated and retain access afterward. The patch adds session ID regeneration on all authentication transitions."
                  },
                  {
                    "cweId": "CWE-287",
                    "rationale": "The session identifier was a bare, predictable numeric user ID with no cryptographic binding to the account\u0027s credentials. This allowed session identifiers to be trivially guessed or forged by anyone who knew a user\u0027s ID, constituting improper authentication. The uncertainty is that the primary impact is session persistence rather than direct forgery, but the root cause is the lack of credential binding in the authentication token."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (a7f025ecfdf60dc0ea3438c79b21a8edc2449836): fix: [security] Revoke browser sessions when credentials",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch"
                    ],
                    "timestamp": "2026-11-02T13:43:10Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/a7f025ecfdf60dc0ea3438c79b21a8edc2449836.patch"
                    ],
                    "timestamp": "2026-11-20T10:19:26.228826Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20365"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133652",
    "datePublished": "2026-11-20T10:24:38.906Z",
    "dateReserved": "2026-11-20T10:24:36.475Z",
    "dateUpdated": "2026-11-20T16:39:25.381Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-132283 (GCVE-0-2026-132283)

Vulnerability from cvelistv5 – Published: 2026-11-19 00:00 – Updated: 2026-11-19 19:30
VLAI
Title
Directus Authentication Service authentication.ts AuthenticationService.refresh session expiration
Summary
A vulnerability was identified in Directus up to 12.7.0. This issue affects the function AuthenticationService.refresh of the file api/src/services/authentication.ts of the component Authentication Service. Such manipulation leads to session expiration. The attack can be launched remotely. The vendor was contacted early about this disclosure.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 19:30 UTC
CWE
Assigner
VulDB CNA under the mitre root
CNA scorecard B 83/100 over 3841 records in the last 180 days details
References
URL Tags
https://vuldb.com/vuln/439653 vdb-entrytechnical-description
https://vuldb.com/vuln/439653/cti signaturepermissions-required
https://vuldb.com/cve/CVE-2026-132283 third-party-advisory
https://vuldb.com/submit/958019 third-party-advisory
https://github.com/godzeo/vulhub/issues/4 broken-linkissue-tracking
Impacted products
Vendor Product Version
n/a Directus Affected: 12.0
Affected: 12.1
Affected: 12.2
Affected: 12.3
Affected: 12.4
Affected: 12.5
Affected: 12.6
Affected: 12.7.0
    cpe:2.3:a:directus:directus:*:*:*:*:*:*:*:*
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-132283",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T19:30:39.531423Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T19:30:47.828Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:directus:directus:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "Authentication Service"
          ],
          "product": "Directus",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "12.0"
            },
            {
              "status": "affected",
              "version": "12.1"
            },
            {
              "status": "affected",
              "version": "12.2"
            },
            {
              "status": "affected",
              "version": "12.3"
            },
            {
              "status": "affected",
              "version": "12.4"
            },
            {
              "status": "affected",
              "version": "12.5"
            },
            {
              "status": "affected",
              "version": "12.6"
            },
            {
              "status": "affected",
              "version": "12.7.0"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Zeo666666 (VulDB User)"
        },
        {
          "lang": "en",
          "type": "coordinator",
          "value": "VulDB CNA Team"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A vulnerability was identified in Directus up to 12.7.0. This issue affects the function AuthenticationService.refresh of the file api/src/services/authentication.ts of the component Authentication Service. Such manipulation leads to session expiration. The attack can be launched remotely. The vendor was contacted early about this disclosure."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "baseScore": 6.9,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X",
            "version": "4.0"
          }
        },
        {
          "cvssV3_1": {
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:C",
            "version": "3.1"
          }
        },
        {
          "cvssV3_0": {
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:X/RL:X/RC:C",
            "version": "3.0"
          }
        },
        {
          "cvssV2_0": {
            "baseScore": 5,
            "vectorString": "AV:N/AC:L/Au:N/C:P/I:N/A:N/E:ND/RL:ND/RC:C",
            "version": "2.0"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-1462",
              "description": "Improper Session Management",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T00:00:40.232Z",
        "orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
        "shortName": "VulDB"
      },
      "references": [
        {
          "name": "VDB-439653 | Directus Authentication Service authentication.ts AuthenticationService.refresh session expiration",
          "tags": [
            "vdb-entry",
            "technical-description"
          ],
          "url": "https://vuldb.com/vuln/439653"
        },
        {
          "name": "VDB-439653 | CTI Indicators (IOB, IOC, IOA)",
          "tags": [
            "signature",
            "permissions-required"
          ],
          "url": "https://vuldb.com/vuln/439653/cti"
        },
        {
          "name": "CVE-2026-132283 | CVE Analysis and Report",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/cve/CVE-2026-132283"
        },
        {
          "name": "Submit #958019 | Directus source revision a6c460a; affected releases to be confirmed Session Expiration",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/submit/958019"
        },
        {
          "tags": [
            "broken-link",
            "issue-tracking"
          ],
          "url": "https://github.com/godzeo/vulhub/issues/4"
        }
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-11-18T00:00:00.000Z",
          "value": "Advisory disclosed"
        },
        {
          "lang": "en",
          "time": "2026-11-18T01:00:00.000Z",
          "value": "VulDB entry created"
        },
        {
          "lang": "en",
          "time": "2026-11-18T18:16:36.000Z",
          "value": "VulDB entry last update"
        }
      ],
      "title": "Directus Authentication Service authentication.ts AuthenticationService.refresh session expiration",
      "x_generator": [
        "VulDB PVTS v202611"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
    "assignerShortName": "VulDB",
    "cveId": "CVE-2026-132283",
    "datePublished": "2026-11-19T00:00:40.232Z",
    "dateReserved": "2026-11-18T17:11:24.181Z",
    "dateUpdated": "2026-11-19T19:30:47.828Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-132079 (GCVE-0-2026-132079)

Vulnerability from cvelistv5 – Published: 2026-11-18 11:57 – Updated: 2026-11-19 21:24
VLAI
Title
Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry
Summary
Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for. This issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0. Users are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.
SSVC
Exploitation: none Automatable: yes Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 21:24 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
apache CNA under the mitre root
CNA scorecard B 76/100 over 1285 records in the last 180 days details
Impacted products
Vendor Product Version
Apache Software Foundation Apache Iggy Go SDK Affected: 0.5.0 , < 0.10.0 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2026-11-18T16:05:09.539Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2026/11/18/6"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "HIGH",
              "baseScore": 9.8,
              "baseSeverity": "CRITICAL",
              "confidentialityImpact": "HIGH",
              "integrityImpact": "HIGH",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2026-132079",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T21:24:08.207539Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T21:24:31.425Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://golang.org/pkg",
          "defaultStatus": "unaffected",
          "packageName": "github.com/apache/iggy/foreign/go",
          "packageURL": "pkg:golang/github.com/apache/iggy/foreign/go",
          "product": "Apache Iggy Go SDK",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "0.10.0",
              "status": "affected",
              "version": "0.5.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Goutam Adwant"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cdiv\u003eInsufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.\u003c/div\u003e\u003cdiv\u003eThis issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.\u003c/div\u003e\u003cdiv\u003eUsers are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones.\u003c/div\u003e"
            }
          ],
          "value": "Insufficient Session Expiration vulnerability in the Apache Iggy Go SDK. The TCP client method CreatePersonalAccessToken wrote the 32-bit expiry into the upper half of the 64-bit expiry field that the server reads. The server read a nonzero expiry as 2^32 times the requested value. A token created through the Go TCP client therefore stayed valid about four billion times longer than the caller asked for.\n\nThis issue affects Apache Iggy Go SDK: from 0.5.0 before 0.10.0.\n\nUsers are recommended to upgrade to version 0.10.0, which fixes the issue. Tokens that an earlier version created keep their long expiry on the server. Delete those tokens and create new ones."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "low"
            },
            "type": "Textual description of severity"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613 Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T11:57:51.156Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/apache/iggy/pull/4615"
        },
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/16fhwkppm51x1vqr3kxo551qx2w5zpkg"
        }
      ],
      "source": {
        "discovery": "EXTERNAL"
      },
      "title": "Apache Iggy Go SDK: Go TCP client creates personal access tokens that outlive the requested expiry",
      "x_generator": {
        "engine": "Vulnogram 1.0.3"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2026-132079",
    "datePublished": "2026-11-18T11:57:51.156Z",
    "dateReserved": "2026-11-18T11:05:37.365Z",
    "dateUpdated": "2026-11-19T21:24:31.425Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-130717 (GCVE-0-2026-130717)

Vulnerability from cvelistv5 – Published: 2026-11-18 11:33 – Updated: 2026-11-21 03:23
VLAI
Title
NocoDB before 2026.04.1 Password Reset Token Not Invalidated on Password Change
Summary
NocoDB before 2026.04.1 fails to clear reset_password_token and reset_password_expires in users.service.ts when a password is changed, leaving earlier reset links valid. Attackers holding an unexpired reset link, such as from prior mailbox access, can set a new password and regain control of the account.
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-21 03:23 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8675 records in the last 180 days details
References
Impacted products
Vendor Product Version
nocodb nocodb Affected: 0 , < 2026.04.1 (custom)
Unaffected: 2026.04.1 (custom)
    cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-02 00:00
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-130717",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-21T03:23:04.174654Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-21T03:23:26.368Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "nocodb",
          "vendor": "nocodb",
          "versions": [
            {
              "lessThan": "2026.04.1",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "status": "unaffected",
              "version": "2026.04.1",
              "versionType": "custom"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2026.04.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "datePublic": "2026-11-02T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "NocoDB before 2026.04.1 fails to clear reset_password_token and reset_password_expires in users.service.ts when a password is changed, leaving earlier reset links valid. Attackers holding an unexpired reset link, such as from prior mailbox access, can set a new password and regain control of the account."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 7.6,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "PASSIVE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T11:33:59.952Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-82pm-w64f-8m6h)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-82pm-w64f-8m6h"
        }
      ],
      "title": "NocoDB before 2026.04.1 Password Reset Token Not Invalidated on Password Change",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-130717",
    "datePublished": "2026-11-18T11:33:59.952Z",
    "dateReserved": "2026-11-17T15:38:37.516Z",
    "dateUpdated": "2026-11-21T03:23:26.368Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-130695 (GCVE-0-2026-130695)

Vulnerability from cvelistv5 – Published: 2026-11-18 11:33 – Updated: 2026-11-21 03:04
VLAI
Title
NocoDB before 2026.10.1 Authentication Bypass via Revoked OAuth Access Tokens
Summary
NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows holders of revoked OAuth access tokens to authenticate as first-party sessions by presenting them through the session header. Attackers can bypass revocation, client-existence, route allowlist and granted_resources scope checks to modify victim profiles, upload to storage, and force global sign-outs.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-21 03:04 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8675 records in the last 180 days details
References
Impacted products
Vendor Product Version
nocodb nocodb Affected: 0 , < 2026.10.1 (semver)
Unaffected: 2026.10.1 (semver)
    cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-02 00:00
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-130695",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-21T03:04:38.447537Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-21T03:04:54.641Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "nocodb",
          "vendor": "nocodb",
          "versions": [
            {
              "lessThan": "2026.10.1",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "2026.10.1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2026.10.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "datePublic": "2026-11-02T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "NocoDB before 2026.10.1 contains an authentication bypass vulnerability that allows holders of revoked OAuth access tokens to authenticate as first-party sessions by presenting them through the session header. Attackers can bypass revocation, client-existence, route allowlist and granted_resources scope checks to modify victim profiles, upload to storage, and force global sign-outs."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "LOW",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T11:33:58.312Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-r872-6prr-v2jc)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-r872-6prr-v2jc"
        }
      ],
      "title": "NocoDB before 2026.10.1 Authentication Bypass via Revoked OAuth Access Tokens",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-130695",
    "datePublished": "2026-11-18T11:33:58.312Z",
    "dateReserved": "2026-11-17T15:37:04.966Z",
    "dateUpdated": "2026-11-21T03:04:54.641Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129706 (GCVE-0-2026-129706)

Vulnerability from cvelistv5 – Published: 2026-11-16 08:46 – Updated: 2026-11-16 14:51
VLAI
Title
vulnerability-lookup: Session Persists After Password Change (CWE-613)
Summary
In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user's credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user's account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation. The affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application. The security impact is that a user cannot effectively revoke an attacker's access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user's profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-16 08:39 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 14:51 UTC
CWE
  • CWE-613 - Session Persistence After Password Change
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version
vulnerability-lookup vulnerability-lookup Affected: unspecified
    cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Partially reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-16 08:39
Model
qwen3.8:27b
Input
https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch e35954004742…
Confidence
medium
Commit Subject Patch SHA-256
d762810fb3b9 fix: [security] A password change ends the user's other e35954004742…
Fix summary

The session identifier is now bound to the user's current password hash. User.get_id() returns a composite string of the form '<user_id>:<digest>', where the digest is an HMAC-SHA256 of the stored password hash keyed with the application SECRET_KEY. The load_user callback validates that the digest in the session matches the digest computed from the user's current password hash using a constant-time comparison (hmac.compare_digest). If the password has changed, the digest no longer matches and the session is rejected, effectively logging out all sessions that were opened under the previous credential. When a user changes their own password through the profile page, they are immediately re-authenticated via login_user() so their current session is renewed with the new digest while all other sessions are invalidated.

Patch summary

In website/models/user.py, a new session_digest() method computes an HMAC-SHA256 of the password hash keyed with SECRET_KEY and returns the first 32 hex characters. User.get_id() is changed from returning the integer self.id to returning the string f'{self.id}:{self.session_digest()}'. In website/web/views/session_mgmt.py, the load_user callback is rewritten to parse the composite session ID, extract the user ID and digest, look up the user, and verify the digest with hmac.compare_digest against the user's current session_digest(); sessions with a bare ID or a mismatched digest are rejected. In website/web/views/user.py, the ineffective session.new = True assignment is removed and replaced with a call to login_user(user) after a password change so the user's own session is renewed. All test files are updated to use user.get_id() instead of user.id when setting the session, and a new test file tests/test_session_password_binding.py verifies that a password change invalidates other sessions, that bare IDs are拒绝

CVSS rationale

AV:N: the application is a network-accessible web service. AC:L: once a valid session is obtained, it persists with no additional complexity; no race conditions or special timing are needed. AT:N: no attack target manipulation is required. PR:L: the attacker must already possess a valid authenticated session for the target user (obtained via XSS, session hijacking, or a previously exposed key). UI:N: no victim interaction is needed after the session is compromised. VC:L: the attacker can read the user's profile data, subscriptions, and role-gated content. VI:L: the attacker can modify the user's profile, subscriptions, and other user-controlled data. VA:L: the attacker can continue to use the service on behalf of the user, and the user cannot revoke access by changing the password. SC/SI/SA:N: no impact on other systems or components is evidenced in the patch.

Weakness rationale
  • CWE-613 The commit message explicitly cites CWE-613. The session ID was the bare user ID with no component tied to the credential, so sessions outlived every password change, account recovery, or admin reset. This is a textbook instance of session persistence after password change.
Attack pattern rationale
  • CAPEC-122 The session identifier was effectively fixed to the static user ID and never rotated or invalidated on credential change. While classic session fixation involves an attacker choosing the session ID, the underlying weakness is the same: the session ID is not bound to the current credential state and cannot be revoked by the user. CAPEC-122 is the closest available pattern; the uncertainty is that the attacker does not choose the ID but rather exploits its permanence. No CAPEC specifically covers 'session outlives credential change' as a distinct pattern, making CAPEC-122 the best available match.
Assumptions to verify
  • The application is assumed to be a standard network-accessible Flask web application; no specific deployment topology, reverse proxy, or authentication gateway is evidenced in the patch.
  • PR:L assumes the attacker must already hold a valid session for the target user. If sessions could be obtained without authentication (e.g., via a feed key or API key that does not require a prior login), PR could be N; the commit message references feed keys and API keys as a vector, but the exact authentication requirements of those keys are not detailed in the patch.
  • The CAPEC-122 mapping is the closest available pattern; no CAPEC specifically describes 'session outlives credential change' as a standalone attack pattern, so the mapping carries inherent uncertainty.
  • Affected version range is unspecified because the patch does not include version tags, release notes, or a changelog entry identifying the first or last affected release.
  • The commit date is 2026-11-16; the fixed version is the commit d762810fb3b9d1ee34938a71cd8cbee544c1527d and all prior commits that lacked the digest-bound session ID.
  • CVSS impact metrics (VC, VI, VA) are rated Low rather than High because the attacker's capabilities are bounded by the permissions the session already carried; the vulnerability does not grant new privileges but prevents revocation of existing ones.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 medium 6
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-15 16:36 UTC Report received maintainer Vulnerability report received by e-mail from the reporter (Michael Reimsbach), against revision 4f181ad9 on main. Besides two token findings, it reports that an existing session is not invalidated when the password or a key changes (CWE-613).
  2. 2026-11-16 07:40 UTC Validated maintainer Report reproduced on revision 4f181ad9: a session stays valid after the user's password, API key and feed key are all changed, because the session identifier is the bare user ID.
  3. 2026-11-16 08:04 UTC Fix developed maintainer Corrective change authored (d762810fb3b9d1ee34938a71cd8cbee544c1527d): fix: [security] A password change ends the user's other sessions. The session identifier is bound to the password hash; sessions holding a bare ID are refused, which also ends the sessions a feed key or an API key could open before 3605d5b6. https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch
  4. 2026-11-16 08:06 UTC Fix available maintainer Fix pushed to the public main branch of the repository, together with 3605d5b6. https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-129706",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T14:51:32.431041Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T14:51:40.485Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "website/models/user.py",
            "website/web/views/session_mgmt.py",
            "website/web/views/user.py"
          ],
          "product": "vulnerability-lookup",
          "programFiles": [
            "website/models/user.py",
            "website/web/views/session_mgmt.py",
            "website/web/views/user.py"
          ],
          "repo": "https://github.com/vulnerability-lookup/vulnerability-lookup",
          "vendor": "vulnerability-lookup",
          "versions": [
            {
              "status": "affected",
              "version": "unspecified"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Michael Reimsbach"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "C\u00e9dric Bonhomme"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the vulnerability-lookup web application, the Flask-Login session identifier was set to the bare numeric user ID (User.get_id() returned self.id). Because the session ID contained no component derived from the user\u0027s credential, it remained valid indefinitely regardless of any subsequent password change, account recovery, or administrator-initiated password reset. An attacker who had obtained a valid session for a user account (for example through cross-site scripting, session hijacking, or a previously exposed feed or API key) could continue to access that user\u0027s account after the user changed their password, because the session cookie still carried the same static user ID and the user_loader accepted it without any credential-bound validation.\n\nThe affected component is the session management layer of the vulnerability-lookup Flask application, specifically the User.get_id() method in website/models/user.py and the load_user callback in website/web/views/session_mgmt.py. The vulnerability required that an attacker already possessed a valid session for the target user; no additional authentication or special deployment configuration was needed beyond a standard deployment of the application.\n\nThe security impact is that a user cannot effectively revoke an attacker\u0027s access by changing their password, performing an account recovery, or having an administrator reset the credential. The attacker retains full authenticated access to the user\u0027s profile, subscriptions, and any role-gated functionality for the lifetime of the session cookie. Additionally, sessions that were opened via a feed key or API key before a prior fix (commit 3605d5b6) also persisted indefinitely."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-122",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-122 Session Fixation"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "LOW",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "partial"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-16T08:39:36Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613 Session Persistence After Password Change",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-16T08:46:47.377Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The session identifier is now bound to the user\u0027s current password hash. User.get_id() returns a composite string of the form \u0027\u003cuser_id\u003e:\u003cdigest\u003e\u0027, where the digest is an HMAC-SHA256 of the stored password hash keyed with the application SECRET_KEY. The load_user callback validates that the digest in the session matches the digest computed from the user\u0027s current password hash using a constant-time comparison (hmac.compare_digest). If the password has changed, the digest no longer matches and the session is rejected, effectively logging out all sessions that were opened under the previous credential. When a user changes their own password through the profile page, they are immediately re-authenticated via login_user() so their current session is renewed with the new digest while all other sessions are invalidated."
        }
      ],
      "title": "vulnerability-lookup: Session Persists After Password Change (CWE-613)",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "partial",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The application is assumed to be a standard network-accessible Flask web application; no specific deployment topology, reverse proxy, or authentication gateway is evidenced in the patch.",
                  "PR:L assumes the attacker must already hold a valid session for the target user. If sessions could be obtained without authentication (e.g., via a feed key or API key that does not require a prior login), PR could be N; the commit message references feed keys and API keys as a vector, but the exact authentication requirements of those keys are not detailed in the patch.",
                  "The CAPEC-122 mapping is the closest available pattern; no CAPEC specifically describes \u0027session outlives credential change\u0027 as a standalone attack pattern, so the mapping carries inherent uncertainty.",
                  "Affected version range is unspecified because the patch does not include version tags, release notes, or a changelog entry identifying the first or last affected release.",
                  "The commit date is 2026-11-16; the fixed version is the commit d762810fb3b9d1ee34938a71cd8cbee544c1527d and all prior commits that lacked the digest-bound session ID.",
                  "CVSS impact metrics (VC, VI, VA) are rated Low rather than High because the attacker\u0027s capabilities are bounded by the permissions the session already carried; the vulnerability does not grant new privileges but prevents revocation of existing ones."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-122",
                    "rationale": "The session identifier was effectively fixed to the static user ID and never rotated or invalidated on credential change. While classic session fixation involves an attacker choosing the session ID, the underlying weakness is the same: the session ID is not bound to the current credential state and cannot be revoked by the user. CAPEC-122 is the closest available pattern; the uncertainty is that the attacker does not choose the ID but rather exploits its permanence. No CAPEC specifically covers \u0027session outlives credential change\u0027 as a distinct pattern, making CAPEC-122 the best available match."
                  }
                ],
                "commit": "d762810fb3b9d1ee34938a71cd8cbee544c1527d",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "Michael Reimsbach"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "C\u00e9dric Bonhomme"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  }
                ],
                "cvssRationale": "AV:N: the application is a network-accessible web service. AC:L: once a valid session is obtained, it persists with no additional complexity; no race conditions or special timing are needed. AT:N: no attack target manipulation is required. PR:L: the attacker must already possess a valid authenticated session for the target user (obtained via XSS, session hijacking, or a previously exposed key). UI:N: no victim interaction is needed after the session is compromised. VC:L: the attacker can read the user\u0027s profile data, subscriptions, and role-gated content. VI:L: the attacker can modify the user\u0027s profile, subscriptions, and other user-controlled data. VA:L: the attacker can continue to use the service on behalf of the user, and the user cannot revoke access by changing the password. SC/SI/SA:N: no impact on other systems or components is evidenced in the patch.",
                "draft": false,
                "fixSummary": "The session identifier is now bound to the user\u0027s current password hash. User.get_id() returns a composite string of the form \u0027\u003cuser_id\u003e:\u003cdigest\u003e\u0027, where the digest is an HMAC-SHA256 of the stored password hash keyed with the application SECRET_KEY. The load_user callback validates that the digest in the session matches the digest computed from the user\u0027s current password hash using a constant-time comparison (hmac.compare_digest). If the password has changed, the digest no longer matches and the session is rejected, effectively logging out all sessions that were opened under the previous credential. When a user changes their own password through the profile page, they are immediately re-authenticated via login_user() so their current session is renewed with the new digest while all other sessions are invalidated.",
                "generatedAt": "2026-11-16T08:39:36.754806Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 6,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "e359540047428f45208a6edd589f39b561414e337fbaf9fcba7f34d63e1dae0f",
                "patchSummary": "In website/models/user.py, a new session_digest() method computes an HMAC-SHA256 of the password hash keyed with SECRET_KEY and returns the first 32 hex characters. User.get_id() is changed from returning the integer self.id to returning the string f\u0027{self.id}:{self.session_digest()}\u0027. In website/web/views/session_mgmt.py, the load_user callback is rewritten to parse the composite session ID, extract the user ID and digest, look up the user, and verify the digest with hmac.compare_digest against the user\u0027s current session_digest(); sessions with a bare ID or a mismatched digest are rejected. In website/web/views/user.py, the ineffective session.new = True assignment is removed and replaced with a call to login_user(user) after a password change so the user\u0027s own session is renewed. All test files are updated to use user.get_id() instead of user.id when setting the session, and a new test file tests/test_session_password_binding.py verifies that a password change invalidates other sessions, that bare IDs are\u62d2\u7edd",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "d762810fb3b9d1ee34938a71cd8cbee544c1527d",
                    "date": "Mon, 16 Nov 2026 09:04:41 +0100",
                    "patchSha256": "e359540047428f45208a6edd589f39b561414e337fbaf9fcba7f34d63e1dae0f",
                    "retrievedAt": "2026-11-16T08:38:48.822217Z",
                    "source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch",
                    "sourceUrl": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch",
                    "subject": "fix: [security] A password change ends the user\u0027s other"
                  }
                ],
                "source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-16T08:39:36Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] A password change ends the user\u0027s other",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-613",
                    "rationale": "The commit message explicitly cites CWE-613. The session ID was the bare user ID with no component tied to the credential, so sessions outlived every password change, account recovery, or admin reset. This is a textbook instance of session persistence after password change."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "actor": "maintainer",
                    "description": "Vulnerability report received by e-mail from the reporter (Michael Reimsbach), against revision 4f181ad9 on main. Besides two token findings, it reports that an existing session is not invalidated when the password or a key changes (CWE-613).",
                    "id": "evt-received-1",
                    "timestamp": "2026-11-15T16:36:10Z",
                    "type": "received"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Report reproduced on revision 4f181ad9: a session stays valid after the user\u0027s password, API key and feed key are all changed, because the session identifier is the bare user ID.",
                    "id": "evt-validated-1",
                    "timestamp": "2026-11-16T07:40:02Z",
                    "type": "validated"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Corrective change authored (d762810fb3b9d1ee34938a71cd8cbee544c1527d): fix: [security] A password change ends the user\u0027s other sessions. The session identifier is bound to the password hash; sessions holding a bare ID are refused, which also ends the sessions a feed key or an API key could open before 3605d5b6.",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d",
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch"
                    ],
                    "timestamp": "2026-11-16T08:04:41Z",
                    "type": "fix-developed"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Fix pushed to the public main branch of the repository, together with 3605d5b6.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d",
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/d762810fb3b9d1ee34938a71cd8cbee544c1527d.patch"
                    ],
                    "timestamp": "2026-11-16T08:06:43Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20340"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-129706",
    "datePublished": "2026-11-16T08:46:47.377Z",
    "dateReserved": "2026-11-16T08:46:40.876Z",
    "dateUpdated": "2026-11-16T14:51:40.485Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129703 (GCVE-0-2026-129703)

Vulnerability from cvelistv5 – Published: 2026-11-16 08:36 – Updated: 2026-11-16 14:55
VLAI
Title
vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA
Summary
In the vulnerability-lookup web application, the authentication decorators for feed-key requests (auth_feedkey_func in website/decorators.py) and API-key requests (auth_func in website/web/api/v1/common.py) called Flask-Login's login_user() function. This caused the HTTP response to a request authenticated solely by a feed key (supplied as the X-FEED-KEY URL parameter) or an API key (supplied as the X-API-KEY header) to set a session cookie that grants full authenticated access to every page in the application, without requiring a password or two-factor authentication. The practical impact is that any party possessing a leaked feed URL (a common occurrence, as feed URLs are shared with RSS readers) or an API key could obtain a valid web session for the associated account. This session provides access to the user's account page, which exposes the API key and other profile data, and for accounts with the administrator role, access to the /admin interface, enabling full administrative control of the application. The vulnerability affects all users whose feed key or API key is exposed. No prior authentication, user interaction, or special network conditions are required; a single HTTP request with the token is sufficient to establish the session. The session persists until it expires, and because it is not bound to the original credential (a related CWE-613 issue noted by the developers), revoking the feed key or API key does not invalidate the already-created session. The fix replaces the login_user() call with assignment to g._login_user, which Flask-Login's current_user property reads for the current request only, without writing any session cookie. The affected views remain unchanged and continue to see the authenticated user for the single request.
SSVC
Exploitation: none Automatable: yes Technical Impact: total
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-16 08:23 UTC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 14:55 UTC
CWE
  • CWE-287 - Improper Authentication
  • CWE-613 - Insufficient Session Expiration
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version
vulnerability-lookup vulnerability-lookup Affected: unspecified
    cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Partially reviewed GNA-1

Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-16 08:23
Model
qwen3.8:27b
Input
https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b.patch 36e0430891b6…
Confidence
high
Commit Subject Patch SHA-256
3605d5b65d34 fix: [security] A feed key or an API key no longer opens a 36e0430891b6…
Fix summary

The authentication decorators for feed-key and API-key requests no longer call Flask-Login's login_user(), which was writing the authenticated user into the session cookie and creating a full web session. Instead, the user object is now stored on Flask's request-scoped g._login_user attribute, which Flask-Login's current_user property reads first. This authenticates only the current request without setting any session cookie, preventing a limited-scope token from being elevated to a persistent, all-pages session that bypasses password and two-factor authentication.

Patch summary

In website/decorators.py (auth_feedkey_func) and website/web/api/v1/common.py (auth_func), the import of login_user from flask_login is removed and replaced with an import of g from flask. The call login_user(user) (or login_user(user, remember=False)) is replaced with g._login_user = user. A new test file tests/test_token_auth_no_session.py is added with four test cases verifying that: (1) a feed-key request returns 200 but sets no session cookie, (2) an API-key request returns 200 but sets no session cookie, (3) a subsequent unauthenticated request to /user/profile is redirected (302), and (4) a 403 response from an API-key request also sets no session cookie.

CVSS rationale

AV:N: The feed key is in a URL and the API key is in a header; both are accessible over the network. AC:L: A single HTTP request with the token is sufficient; no race conditions or special timing required. AT:N: No manipulation of the target system is needed. PR:N: No prior authentication is required; the token itself is the credential, and it is not protected by any additional gate. UI:N: No user interaction is needed. VC/VI/VA:N: The vulnerable component (the authentication layer) is not itself compromised in terms of its own data, integrity, or availability. SC:H: The attacker gains full read access to the user's account data, including the API key and profile information. SI:H: The attacker can modify the user's account settings, and for administrator accounts, can perform arbitrary administrative actions via /admin. SA:N: No availability impact on the user's account or the application is demonstrated by the evidence.

Weakness rationale
  • CWE-287 The authentication mechanism improperly elevated a limited-scope credential (feed key or API key intended for single-request authentication) into a full web session via login_user(), bypassing password and two-factor authentication. The authentication check succeeded but the session establishment was incorrect for the credential type.
  • CWE-613 The commit message explicitly references CWE-613 as a related concern: sessions created before the fix remain valid until they expire and are not bound to the original credential. While the primary fix addresses the session creation, the lack of credential binding in existing sessions is a secondary weakness acknowledged by the developers.
Attack pattern rationale
  • CAPEC-63 The feed key and API key are trusted credentials for specific, limited-scope access (feed delivery, API calls). The vulnerable implementation incorrectly leveraged that trust to establish a full web session, extending the credential's authority beyond its intended scope. This is the closest CAPEC to the pattern of a limited credential being used to gain broader access than intended. Uncertainty: no CAPEC precisely describes 'token authentication creating an unintended persistent session'; CAPEC-63 is the best available match for trust-scope escalation.
Assumptions to verify
  • The application is assumed to be a self-hosted or publicly accessible web service; the patch does not specify deployment topology.
  • No specific version numbers are available from the patch; the affected version range is unspecified.
  • The CVSS sub-component impact (SC:H, SI:H) assumes the worst case where the authenticated account has administrative privileges, granting access to /admin. For non-admin accounts, the impact is limited to the user's own account data.
  • The CAPEC-63 mapping is the closest available match; no CAPEC precisely describes a limited-scope token being elevated to a full session via an improper login_user() call.
  • The commit message notes that pre-existing sessions created before the fix remain valid until expiration and are not bound to the credential (CWE-613); this is acknowledged as a separate issue not addressed by this patch.
  • The 'Co-Authored-By: Claude Opus 5.5' credit is included as a tool credit based on the explicit commit message; it is unclear whether this represents meaningful remediation contribution or automated assistance.
  • The patch does not indicate whether the application requires TLS or any other transport-level protection; CVSS assumes standard network access.
Model comparison

Selected qwen3.8:27b by deterministic-consensus-v1
The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required.

Model Score Agreement Confidence Assumptions
qwen3.8:27b 6 11 high 7
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-15 16:36 UTC Report received maintainer Vulnerability report received by e-mail from the reporter.
  2. 2026-11-16 07:40 UTC Validated maintainer Report reproduced: a feed key or an API key opens a full web session, which also bypasses two-factor authentication.
  3. 2026-11-16 07:56 UTC Fix developed maintainer Corrective change authored (3605d5b6): a feed key or an API key no longer opens a web session. https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b
  4. 2026-11-16 08:06 UTC Fix available maintainer Fix pushed to the public main branch. https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-129703",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T14:55:15.356568Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T14:55:24.289Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "website/decorators.py (auth_feedkey_func)",
            "website/web/api/v1/common.py (auth_func)"
          ],
          "product": "vulnerability-lookup",
          "programFiles": [
            "website/decorators.py",
            "website/web/api/v1/common.py"
          ],
          "repo": "https://github.com/vulnerability-lookup/vulnerability-lookup",
          "vendor": "vulnerability-lookup",
          "versions": [
            {
              "status": "affected",
              "version": "unspecified"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:vulnerability-lookup:vulnerability-lookup:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Michael Reimsbach"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "C\u00e9dric Bonhomme"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Claude Opus 5.5"
        },
        {
          "lang": "en",
          "type": "tool",
          "value": "Claude Opus 5.5"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the vulnerability-lookup web application, the authentication decorators for feed-key requests (auth_feedkey_func in website/decorators.py) and API-key requests (auth_func in website/web/api/v1/common.py) called Flask-Login\u0027s login_user() function. This caused the HTTP response to a request authenticated solely by a feed key (supplied as the X-FEED-KEY URL parameter) or an API key (supplied as the X-API-KEY header) to set a session cookie that grants full authenticated access to every page in the application, without requiring a password or two-factor authentication.\n\nThe practical impact is that any party possessing a leaked feed URL (a common occurrence, as feed URLs are shared with RSS readers) or an API key could obtain a valid web session for the associated account. This session provides access to the user\u0027s account page, which exposes the API key and other profile data, and for accounts with the administrator role, access to the /admin interface, enabling full administrative control of the application.\n\nThe vulnerability affects all users whose feed key or API key is exposed. No prior authentication, user interaction, or special network conditions are required; a single HTTP request with the token is sufficient to establish the session. The session persists until it expires, and because it is not bound to the original credential (a related CWE-613 issue noted by the developers), revoking the feed key or API key does not invalidate the already-created session.\n\nThe fix replaces the login_user() call with assignment to g._login_user, which Flask-Login\u0027s current_user property reads for the current request only, without writing any session cookie. The affected views remain unchanged and continue to see the authenticated user for the single request."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-63",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-63 Leverage Trusted Relationships"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "HIGH",
            "subIntegrityImpact": "HIGH",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        },
        {
          "format": "SSVC",
          "other": {
            "content": {
              "options": [
                {
                  "Exploitation": "none"
                },
                {
                  "Automatable": "yes"
                },
                {
                  "Technical Impact": "total"
                }
              ],
              "role": "Supplier",
              "timestamp": "2026-11-16T08:23:33Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-287",
              "description": "CWE-287 Improper Authentication",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613 Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-16T08:36:51.005Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The authentication decorators for feed-key and API-key requests no longer call Flask-Login\u0027s login_user(), which was writing the authenticated user into the session cookie and creating a full web session. Instead, the user object is now stored on Flask\u0027s request-scoped g._login_user attribute, which Flask-Login\u0027s current_user property reads first. This authenticates only the current request without setting any session cookie, preventing a limited-scope token from being elevated to a persistent, all-pages session that bypasses password and two-factor authentication."
        }
      ],
      "title": "vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "partial",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The application is assumed to be a self-hosted or publicly accessible web service; the patch does not specify deployment topology.",
                  "No specific version numbers are available from the patch; the affected version range is unspecified.",
                  "The CVSS sub-component impact (SC:H, SI:H) assumes the worst case where the authenticated account has administrative privileges, granting access to /admin. For non-admin accounts, the impact is limited to the user\u0027s own account data.",
                  "The CAPEC-63 mapping is the closest available match; no CAPEC precisely describes a limited-scope token being elevated to a full session via an improper login_user() call.",
                  "The commit message notes that pre-existing sessions created before the fix remain valid until expiration and are not bound to the credential (CWE-613); this is acknowledged as a separate issue not addressed by this patch.",
                  "The \u0027Co-Authored-By: Claude Opus 5.5\u0027 credit is included as a tool credit based on the explicit commit message; it is unclear whether this represents meaningful remediation contribution or automated assistance.",
                  "The patch does not indicate whether the application requires TLS or any other transport-level protection; CVSS assumes standard network access."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-63",
                    "rationale": "The feed key and API key are trusted credentials for specific, limited-scope access (feed delivery, API calls). The vulnerable implementation incorrectly leveraged that trust to establish a full web session, extending the credential\u0027s authority beyond its intended scope. This is the closest CAPEC to the pattern of a limited credential being used to gain broader access than intended. Uncertainty: no CAPEC precisely describes \u0027token authentication creating an unintended persistent session\u0027; CAPEC-63 is the best available match for trust-scope escalation."
                  }
                ],
                "commit": "3605d5b65d340343cc4b612d40d454afed84302b",
                "confidence": "high",
                "credits": [
                  {
                    "lang": "en",
                    "type": "reporter",
                    "value": "Michael Reimsbach"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "C\u00e9dric Bonhomme"
                  },
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "Claude Opus 5.5"
                  },
                  {
                    "lang": "en",
                    "type": "tool",
                    "value": "Claude Opus 5.5"
                  }
                ],
                "cvssRationale": "AV:N: The feed key is in a URL and the API key is in a header; both are accessible over the network. AC:L: A single HTTP request with the token is sufficient; no race conditions or special timing required. AT:N: No manipulation of the target system is needed. PR:N: No prior authentication is required; the token itself is the credential, and it is not protected by any additional gate. UI:N: No user interaction is needed. VC/VI/VA:N: The vulnerable component (the authentication layer) is not itself compromised in terms of its own data, integrity, or availability. SC:H: The attacker gains full read access to the user\u0027s account data, including the API key and profile information. SI:H: The attacker can modify the user\u0027s account settings, and for administrator accounts, can perform arbitrary administrative actions via /admin. SA:N: No availability impact on the user\u0027s account or the application is demonstrated by the evidence.",
                "draft": false,
                "fixSummary": "The authentication decorators for feed-key and API-key requests no longer call Flask-Login\u0027s login_user(), which was writing the authenticated user into the session cookie and creating a full web session. Instead, the user object is now stored on Flask\u0027s request-scoped g._login_user attribute, which Flask-Login\u0027s current_user property reads first. This authenticates only the current request without setting any session cookie, preventing a limited-scope token from being elevated to a persistent, all-pages session that bypasses password and two-factor authentication.",
                "generatedAt": "2026-11-16T08:23:33.762073Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 7,
                      "confidence": "high",
                      "model": "qwen3.8:27b",
                      "score": 6
                    }
                  ],
                  "selectedModel": "qwen3.8:27b",
                  "selectionMethod": "deterministic-consensus-v1",
                  "selectionNotice": "The selected result is closest to model consensus; this heuristic does not establish factual correctness and human review remains required."
                },
                "patchSha256": "36e0430891b60133c5817b45b93b89bb0cb70af762b9b90382b646f9c4ed5a33",
                "patchSummary": "In website/decorators.py (auth_feedkey_func) and website/web/api/v1/common.py (auth_func), the import of login_user from flask_login is removed and replaced with an import of g from flask. The call login_user(user) (or login_user(user, remember=False)) is replaced with g._login_user = user. A new test file tests/test_token_auth_no_session.py is added with four test cases verifying that: (1) a feed-key request returns 200 but sets no session cookie, (2) an API-key request returns 200 but sets no session cookie, (3) a subsequent unauthenticated request to /user/profile is redirected (302), and (4) a 403 response from an API-key request also sets no session cookie.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "3605d5b65d340343cc4b612d40d454afed84302b",
                    "date": "Mon, 16 Nov 2026 08:56:35 +0100",
                    "patchSha256": "36e0430891b60133c5817b45b93b89bb0cb70af762b9b90382b646f9c4ed5a33",
                    "retrievedAt": "2026-11-16T08:22:31.738779Z",
                    "source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b.patch",
                    "sourceUrl": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b.patch",
                    "subject": "fix: [security] A feed key or an API key no longer opens a"
                  }
                ],
                "source": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b.patch",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "total"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-16T08:23:33Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] A feed key or an API key no longer opens a",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-287",
                    "rationale": "The authentication mechanism improperly elevated a limited-scope credential (feed key or API key intended for single-request authentication) into a full web session via login_user(), bypassing password and two-factor authentication. The authentication check succeeded but the session establishment was incorrect for the credential type."
                  },
                  {
                    "cweId": "CWE-613",
                    "rationale": "The commit message explicitly references CWE-613 as a related concern: sessions created before the fix remain valid until they expire and are not bound to the original credential. While the primary fix addresses the session creation, the lack of credential binding in existing sessions is a secondary weakness acknowledged by the developers."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "actor": "maintainer",
                    "description": "Vulnerability report received by e-mail from the reporter.",
                    "id": "evt-received-1",
                    "timestamp": "2026-11-15T16:36:10Z",
                    "type": "received"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Report reproduced: a feed key or an API key opens a full web session, which also bypasses two-factor authentication.",
                    "id": "evt-validated-1",
                    "timestamp": "2026-11-16T07:40:02Z",
                    "type": "validated"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Corrective change authored (3605d5b6): a feed key or an API key no longer opens a web session.",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b"
                    ],
                    "timestamp": "2026-11-16T07:56:35Z",
                    "type": "fix-developed"
                  },
                  {
                    "actor": "maintainer",
                    "description": "Fix pushed to the public main branch.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b"
                    ],
                    "timestamp": "2026-11-16T08:06:43Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "gcve-1-2026-20245"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-129703",
    "datePublished": "2026-11-16T08:36:51.005Z",
    "dateReserved": "2026-11-16T08:36:44.944Z",
    "dateUpdated": "2026-11-16T14:55:24.289Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128359 (GCVE-0-2026-128359)

Vulnerability from cvelistv5 – Published: 2026-11-15 21:14 – Updated: 2026-11-16 21:28
VLAI
Title
Gitea OAuth2 provider tokens issued to disabled users
Summary
When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 21:28 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
Gitea CNA under the mitre root
CNA scorecard C 61/100 over 205 records in the last 180 days details
Impacted products
Vendor Product Version
Gitea Gitea Affected: 0 , < 28.4.0 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "NETWORK",
              "availabilityImpact": "NONE",
              "baseScore": 5.4,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "LOW",
              "integrityImpact": "LOW",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2026-128359",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T21:28:54.863147Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T21:28:58.305Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageName": "gitea.dev",
          "product": "Gitea",
          "vendor": "Gitea",
          "versions": [
            {
              "lessThan": "28.4.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "https://github.com/yagcioglutoprak"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "https://github.com/silverwind"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "When Gitea acts as an OAuth2 or OpenID Connect provider, the token endpoint did not check the state of the user. After an administrator deactivated an account or prohibited its sign-in, existing refresh tokens and unused authorization codes of that user could still be exchanged for new tokens, so applications that sign users in through Gitea kept them signed in. The token endpoint now refuses users who may not sign in, and token introspection reports their tokens as inactive."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613: Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-15T21:14:14.486Z",
        "orgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
        "shortName": "Gitea"
      },
      "references": [
        {
          "name": "GitHub Security Advisory GHSA-jrjr-q3rq-f899",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/go-gitea/gitea/security/advisories/GHSA-jrjr-q3rq-f899"
        },
        {
          "name": "Fix: go-gitea/gitea pull request #40131",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40131"
        },
        {
          "name": "Fix backport to release/v28: go-gitea/gitea pull request #40281",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/go-gitea/gitea/pull/40281"
        },
        {
          "name": "Gitea 28.4.0 release announcement",
          "tags": [
            "release-notes"
          ],
          "url": "https://blog.gitea.com/release-of-28.4.0/"
        },
        {
          "name": "go-gitea/gitea v28.4.0 release",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/go-gitea/gitea/releases/tag/v28.4.0"
        }
      ],
      "title": "Gitea OAuth2 provider tokens issued to disabled users"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "88ee5874-cf24-4952-aea0-31affedb7ff2",
    "assignerShortName": "Gitea",
    "cveId": "CVE-2026-128359",
    "datePublished": "2026-11-15T21:14:14.486Z",
    "dateReserved": "2026-11-15T20:31:51.070Z",
    "dateUpdated": "2026-11-16T21:28:58.305Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128335 (GCVE-0-2026-128335)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:33 – Updated: 2026-11-13 16:02
VLAI
Title
Contao before 5.3.54, 5.7.17, and 6.0.6 Session Invalidation Failure on 2FA Change
Summary
Contao 4.6.0 before 5.3.54, 5.4.0-RC1 before 5.7.17, and 6.0.0-RC1 before 6.0.6 fails to invalidate existing user sessions when two-factor authentication is enabled or disabled. Because Contao\User::isEqualTo() and serialized session data omit two-factor state, attackers already holding a session keep it after the owner changes 2FA settings.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 15:29 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8675 records in the last 180 days details
Impacted products
Vendor Product Version
Contao Contao Affected: 4.6.0 , < 5.3.54 (semver)
Affected: 5.4.0-RC1 , < 5.7.17 (semver)
Affected: 6.0.0-RC1 , < 6.0.6 (semver)
    cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*
    cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*
    cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-11 07:19
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-128335",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T15:29:09.845342Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T16:02:22.251Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:composer/contao/core-bundle",
          "product": "Contao",
          "vendor": "Contao",
          "versions": [
            {
              "lessThan": "5.3.54",
              "status": "affected",
              "version": "4.6.0",
              "versionType": "semver"
            },
            {
              "lessThan": "5.7.17",
              "status": "affected",
              "version": "5.4.0-RC1",
              "versionType": "semver"
            },
            {
              "lessThan": "6.0.6",
              "status": "affected",
              "version": "6.0.0-RC1",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.3.54",
                  "versionStartIncluding": "4.6.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.7.17",
                  "versionStartIncluding": "5.4.0-rc1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:contao:contao:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.6",
                  "versionStartIncluding": "6.0.0-rc1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Farhan Khan"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Martin Ausw\u00f6ger"
        }
      ],
      "datePublic": "2026-11-11T07:19:47.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Contao 4.6.0 before 5.3.54, 5.4.0-RC1 before 5.7.17, and 6.0.0-RC1 before 6.0.6 fails to invalidate existing user sessions when two-factor authentication is enabled or disabled. Because Contao\\User::isEqualTo() and serialized session data omit two-factor state, attackers already holding a session keep it after the owner changes 2FA settings."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 2.1,
            "baseSeverity": "LOW",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "PASSIVE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 3.7,
            "baseSeverity": "LOW",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:33:39.011Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-5mg3-mv6j-57wc)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/contao/contao/security/advisories/GHSA-5mg3-mv6j-57wc"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/contao/contao/commit/7e7c821ce6c41c02ae85b3d9f8eff5039de3fe1e"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/contao/contao/commit/7618a5757347a30168139e74c7b326e3e296059d"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/contao/contao/commit/843da308056402d94ae2dbb999959f9e2ce71fe1"
        },
        {
          "name": "Contao 5.3.54 Release Notes",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/contao/contao/releases/tag/5.3.54"
        },
        {
          "name": "Contao 5.7.17 Release Notes",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/contao/contao/releases/tag/5.7.17"
        },
        {
          "name": "Contao 6.0.6 Release Notes",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/contao/contao/releases/tag/6.0.6"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/contao/contao/blob/5.3.53/core-bundle/contao/library/Contao/User.php#L413-L446"
        },
        {
          "name": "VulnCheck Advisory: Contao before 5.3.54, 5.7.17, and 6.0.6 Session Invalidation Failure on 2FA Change",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/contao-before-5.3.54-5.7.17-and-6.0.6-session-invalidation-failure-on-2fa-change"
        }
      ],
      "title": "Contao before 5.3.54, 5.7.17, and 6.0.6 Session Invalidation Failure on 2FA Change",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-128335",
    "datePublished": "2026-11-13T09:33:39.011Z",
    "dateReserved": "2026-11-13T01:20:38.188Z",
    "dateUpdated": "2026-11-13T16:02:22.251Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128330 (GCVE-0-2026-128330)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:33 – Updated: 2026-11-17 13:18
VLAI
Title
Miniflux before 2.3.5 Insufficient Session Expiration After Password Change
Summary
Miniflux before 2.3.5 contains an insufficient session expiration vulnerability that allows attackers to retain account access because password changes do not revoke existing web sessions. Attackers holding a leaked password or copied session cookie keep access for up to 30 days, reading integration credentials, creating API keys, or registering passkeys.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 13:18 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8675 records in the last 180 days details
Impacted products
Vendor Product Version
miniflux miniflux Affected: 0 , < 2.3.5 (semver)
    cpe:2.3:a:miniflux_project:miniflux:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-11-12 04:34
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-128330",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-17T13:18:22.860527Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-17T13:18:56.156Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:golang/miniflux.app/v2",
          "product": "miniflux",
          "vendor": "miniflux",
          "versions": [
            {
              "lessThan": "2.3.5",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:miniflux_project:miniflux:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2.3.5",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Sandipkumar sah"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Fr\u00e9d\u00e9ric Guillot"
        }
      ],
      "datePublic": "2026-11-12T04:34:34.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Miniflux before 2.3.5 contains an insufficient session expiration vulnerability that allows attackers to retain account access because password changes do not revoke existing web sessions. Attackers holding a leaked password or copied session cookie keep access for up to 30 days, reading integration credentials, creating API keys, or registering passkeys."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "privilegesRequired": "LOW",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.2,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:33:43.522Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-ch38-3q93-fwg8)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/miniflux/v2/security/advisories/GHSA-ch38-3q93-fwg8"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/miniflux/v2/commit/229035a4df6e60107d1117eb50696b23e08cb4b8"
        },
        {
          "tags": [
            "issue-tracking",
            "patch"
          ],
          "url": "https://github.com/miniflux/v2/pull/4594"
        },
        {
          "name": "miniflux v2.3.5 Release Notes",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/miniflux/v2/releases/tag/v2.3.5"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/miniflux/v2/blob/v2.3.4/internal/storage/user.go#L174-L190"
        },
        {
          "name": "VulnCheck Advisory: Miniflux before 2.3.5 Insufficient Session Expiration After Password Change",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/miniflux-before-2.3.5-insufficient-session-expiration-after-password-change"
        }
      ],
      "title": "Miniflux before 2.3.5 Insufficient Session Expiration After Password Change",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-128330",
    "datePublished": "2026-11-13T09:33:43.522Z",
    "dateReserved": "2026-11-13T01:20:36.385Z",
    "dateUpdated": "2026-11-17T13:18:56.156Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

No mitigation information available for this CWE.

No CAPEC attack patterns related to this CWE.