Common Weakness Enumeration

CWE-613

Allowed-with-Review

Insufficient Session Expiration

Abstraction: Base · Status: Incomplete

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

1161 vulnerabilities reference this CWE, most recent first.

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
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
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-15 21:14
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.
Severity
No CVSS data available.
CWE
  • CWE-613 - Insufficient Session Expiration
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": {
    "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-15T21:14:14.486Z",
    "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
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-13 09:33
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.
CWE
  • CWE-613 - Insufficient Session Expiration
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": {
    "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-13T09:33:43.522Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128030 (GCVE-0-2026-128030)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:34 – Updated: 2026-11-13 09:34
VLAI
Title
OpenMage magento-lts before 20.18.2 Insufficient Session Expiration After API User Deactivation
Summary
OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration vulnerability because Mage_Api_Model_Session::_renewBySessId() never checks api_user.is_active and REST OAuth authorization never checks whether the admin user is active. Attackers holding an existing SOAP/XML-RPC session or OAuth access token retain API access after deactivation or API key rotation, reading and modifying customer, order and catalog data.
CWE
  • CWE-613 - Insufficient Session Expiration
Impacted products
Vendor Product Version
OpenMage magento-lts Affected: 0 , < 20.18.2 (semver)
Unaffected: 20.18.2 (semver)
Create a notification for this product.
OpenMage magento-lts Affected: 21.0.0-beta1 , < 21.0.0-beta3 (semver)
Unaffected: 21.0.0-beta3 (semver)
Create a notification for this product.
Date Public
2026-10-26 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "magento-lts",
          "vendor": "OpenMage",
          "versions": [
            {
              "lessThan": "20.18.2",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "20.18.2",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "magento-lts",
          "vendor": "OpenMage",
          "versions": [
            {
              "lessThan": "21.0.0-beta3",
              "status": "affected",
              "version": "21.0.0-beta1",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "21.0.0-beta3",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "colinmollenhour"
        }
      ],
      "datePublic": "2026-10-26T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "OpenMage magento-lts before 20.18.2 and 21.0.0-beta1 before 21.0.0-beta3 contains an insufficient session expiration vulnerability because Mage_Api_Model_Session::_renewBySessId() never checks api_user.is_active and REST OAuth authorization never checks whether the admin user is active. Attackers holding an existing SOAP/XML-RPC session or OAuth access token retain API access after deactivation or API key rotation, reading and modifying customer, order and catalog data."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 7.4,
            "baseSeverity": "HIGH",
            "privilegesRequired": "HIGH",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/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": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "HIGH",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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-13T09:34:01.082Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-rrhg-c635-fmrm)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/OpenMage/magento-lts/security/advisories/GHSA-rrhg-c635-fmrm"
        },
        {
          "name": "Patch Commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/OpenMage/magento-lts/commit/73048b7d8380fefb423869342c708ac30f80bc4b"
        },
        {
          "name": "Patch Commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/OpenMage/magento-lts/commit/9daf2c647759816ade7be2c906f08f56cb43a864"
        },
        {
          "name": "VulnCheck Advisory: OpenMage magento-lts before 20.18.2 Insufficient Session Expiration After API User Deactivation",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.18.2-insufficient-session-expiration-after-api-user-deactivation"
        }
      ],
      "title": "OpenMage magento-lts before 20.18.2 Insufficient Session Expiration After API User Deactivation",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-128030",
    "datePublished": "2026-11-13T09:34:01.082Z",
    "dateReserved": "2026-11-12T20:33:43.125Z",
    "dateUpdated": "2026-11-13T09:34:01.082Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126658 (GCVE-0-2026-126658)

Vulnerability from cvelistv5 – Published: 2026-11-11 12:24 – Updated: 2026-11-14 13:05
VLAI
Title
ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys
Summary
ByteStash 1.5.10 before 1.6.2 contains an insufficient session expiration vulnerability that allows holders of API keys to keep access after account deactivation because validateApiKey never checks account status. Attackers holding a deactivated account's API key can read, create, modify and delete its snippets via /api/snippets and use every MCP tool via /mcp.
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 17:11 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Impacted products
Vendor Product Version
jordan-dalby ByteStash Affected: 1.5.10 , < 1.6.2 (semver)
Unaffected: 1.6.2 (semver)
Create a notification for this product.
Date Public
2026-11-10 11:33
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126658",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T17:11:13.917901Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T17:11:57.941Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://github.com/jordan-dalby/ByteStash/security/advisories/GHSA-26m9-ww2j-3cr5"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:github/jordan-dalby/ByteStash",
          "product": "ByteStash",
          "repo": "https://github.com/jordan-dalby/ByteStash",
          "vendor": "jordan-dalby",
          "versions": [
            {
              "lessThan": "1.6.2",
              "status": "affected",
              "version": "1.5.10",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.6.2",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Adib Farhan"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Jordan Dalby"
        }
      ],
      "datePublic": "2026-11-10T11:33:37.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "ByteStash 1.5.10 before 1.6.2 contains an insufficient session expiration vulnerability that allows holders of API keys to keep access after account deactivation because validateApiKey never checks account status. Attackers holding a deactivated account\u0027s API key can read, create, modify and delete its snippets via /api/snippets and use every MCP tool via /mcp."
        }
      ],
      "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:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "LOW",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "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"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-14T13:05:32.828Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-26m9-ww2j-3cr5)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/jordan-dalby/ByteStash/security/advisories/GHSA-26m9-ww2j-3cr5"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/jordan-dalby/ByteStash/commit/eb4ecdfc30f2e7d1424137fa7fe3a9eed663218b"
        },
        {
          "name": "ByteStash v1.6.2 Release Notes",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/jordan-dalby/ByteStash/releases/tag/v1.6.2"
        },
        {
          "tags": [
            "technical-description"
          ],
          "url": "https://github.com/jordan-dalby/ByteStash/blob/v1.6.1/server/src/repositories/apiKeyRepository.js#L70-L78"
        },
        {
          "name": "NetbyteSEC Advisory NBS-2026-0003",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://notes.netbytesec.com/2026/11/cve-2026-126658-bytestash-1510-before.html"
        },
        {
          "name": "VulnCheck Advisory: ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/bytestash-1.5.10-before-1.6.2-insufficient-session-expiration-via-api-keys"
        }
      ],
      "title": "ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126658",
    "datePublished": "2026-11-11T12:24:35.975Z",
    "dateReserved": "2026-11-11T11:58:21.462Z",
    "dateUpdated": "2026-11-14T13:05:32.828Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126453 (GCVE-0-2026-126453)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:35 – Updated: 2026-11-13 09:35
VLAI
Title
OpenEMR before 8.5.0 Inverted Document Expiration Check Exposes PHI via FHIR Binary
Summary
OpenEMR before 8.5.0 contains an inverted comparison in Document::has_expired() that causes the FHIR Binary download endpoint to treat time-limited PHI documents as unexpired after their one-hour lifetime. Authenticated users still authorized for a Binary/{id} resource can download expired bulk export NDJSON files and $docref CCDs indefinitely.
CWE
  • CWE-613 - Insufficient Session Expiration
References
Impacted products
Vendor Product Version
openemr openemr Affected: 0 , < 8.5.0 (semver)
Unaffected: 8.5.0 (semver)
    cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-10-28 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "openemr",
          "vendor": "openemr",
          "versions": [
            {
              "lessThan": "8.5.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "8.5.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "8.5.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Sharwinreddy"
        },
        {
          "lang": "en",
          "type": "reporter",
          "value": "sriharsha1994"
        }
      ],
      "datePublic": "2026-10-28T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "OpenEMR before 8.5.0 contains an inverted comparison in Document::has_expired() that causes the FHIR Binary download endpoint to treat time-limited PHI documents as unexpired after their one-hour lifetime. Authenticated users still authorized for a Binary/{id} resource can download expired bulk export NDJSON files and $docref CCDs indefinitely."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "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:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:35:11.338Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-fp98-qfh5-xjhc)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/openemr/openemr/security/advisories/GHSA-fp98-qfh5-xjhc"
        },
        {
          "name": "VulnCheck Advisory: OpenEMR before 8.5.0 Inverted Document Expiration Check Exposes PHI via FHIR Binary",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/openemr-before-8.5.0-inverted-document-expiration-check-exposes-phi-via-fhir-binary"
        }
      ],
      "title": "OpenEMR before 8.5.0 Inverted Document Expiration Check Exposes PHI via FHIR Binary",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126453",
    "datePublished": "2026-11-13T09:35:11.338Z",
    "dateReserved": "2026-11-10T21:39:26.377Z",
    "dateUpdated": "2026-11-13T09:35:11.338Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126427 (GCVE-0-2026-126427)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:35 – Updated: 2026-11-13 15:56
VLAI
Title
OpenEMR before 8.5.0 Idle Session Timeout Bypass via Eye Exam Form
Summary
OpenEMR before 8.5.0 contains a session expiration vulnerability that prevents automatic logoff because the Eye Exam form's read-only poll omits skip_timeout_reset. Attackers with physical access to an unattended workstation can use the still-active session to view patient health information, since update_READONLY() resets the idle timer every 15 seconds.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 15:30 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
References
Impacted products
Vendor Product Version
openemr openemr Affected: 0 , < 8.5.0 (semver)
Unaffected: 8.5.0 (semver)
    cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-10-28 00:00
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126427",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T15:30:10.870766Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T15:56:10.054Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "openemr",
          "vendor": "openemr",
          "versions": [
            {
              "lessThan": "8.5.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "8.5.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "8.5.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Firehed"
        }
      ],
      "datePublic": "2026-10-28T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "OpenEMR before 8.5.0 contains a session expiration vulnerability that prevents automatic logoff because the Eye Exam form\u0027s read-only poll omits skip_timeout_reset. Attackers with physical access to an unattended workstation can use the still-active session to view patient health information, since update_READONLY() resets the idle timer every 15 seconds."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "PHYSICAL",
            "baseScore": 4.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "PASSIVE",
            "vectorString": "CVSS:4.0/AV:P/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "PHYSICAL",
            "availabilityImpact": "NONE",
            "baseScore": 4.6,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:H/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:35:29.043Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-fc6f-f47r-j9x8)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/openemr/openemr/security/advisories/GHSA-fc6f-f47r-j9x8"
        },
        {
          "name": "VulnCheck Advisory: OpenEMR before 8.5.0 Idle Session Timeout Bypass via Eye Exam Form",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/openemr-before-8.5.0-idle-session-timeout-bypass-via-eye-exam-form"
        }
      ],
      "title": "OpenEMR before 8.5.0 Idle Session Timeout Bypass via Eye Exam Form",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126427",
    "datePublished": "2026-11-13T09:35:29.043Z",
    "dateReserved": "2026-11-10T21:36:07.090Z",
    "dateUpdated": "2026-11-13T15:56:10.054Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126076 (GCVE-0-2026-126076)

Vulnerability from cvelistv5 – Published: 2026-11-10 20:57 – Updated: 2026-11-12 19:05
VLAI
Title
Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore
Summary
Action Pack is a framework for handling and responding to web requests. Prior to 8.1.4.1 and 8.0.5.2, ActionDispatch::Session::CacheStore writes a session back to the cache at the end of each request that loaded it, without checking that the session's cache entry still exists. When a concurrent request destroys the session, through reset_session on logout or by deleting its cache entry on the server, a request that loaded the session earlier and finishes later restores it under its original session ID. Logout and server-side revocation could therefore fail to end a session, and an attacker who holds a stolen session cookie could keep that session valid across the victim's logout. Applications that use config.session_store :cache_store are affected, with any cache backend. ActionDispatch::Session::CookieStore is not affected, nor is ActionDispatch::Session::MemCacheStore with Dalli 4.0.0 or later, whose session store does not write back a session that was deleted. This issue is fixed in versions 8.1.4.1 and 8.0.5.2.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-12 19:04 UTC
CWE
  • CWE-613 - Insufficient Session Expiration
Impacted products
Vendor Product Version
rails rails Affected: >= 8.1, < 8.1.4.1
Affected: < 8.0.5.2
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126076",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-12T19:04:57.165186Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-12T19:05:13.367Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "rails",
          "vendor": "rails",
          "versions": [
            {
              "status": "affected",
              "version": "\u003e= 8.1, \u003c 8.1.4.1"
            },
            {
              "status": "affected",
              "version": "\u003c 8.0.5.2"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Action Pack is a framework for handling and responding to web requests. Prior to 8.1.4.1 and 8.0.5.2, ActionDispatch::Session::CacheStore writes a session back to the cache at the end of each request that loaded it, without checking that the session\u0027s cache entry still exists. When a concurrent request destroys the session, through reset_session on logout or by deleting its cache entry on the server, a request that loaded the session earlier and finishes later restores it under its original session ID. Logout and server-side revocation could therefore fail to end a session, and an attacker who holds a stolen session cookie could keep that session valid across the victim\u0027s logout. Applications that use config.session_store :cache_store are affected, with any cache backend. ActionDispatch::Session::CookieStore is not affected, nor is ActionDispatch::Session::MemCacheStore with Dalli 4.0.0 or later, whose session store does not write back a session that was deleted. This issue is fixed in versions 8.1.4.1 and 8.0.5.2."
        }
      ],
      "metrics": [
        {
          "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"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-613",
              "description": "CWE-613: Insufficient Session Expiration",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-10T20:57:07.582Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/rails/rails/security/advisories/GHSA-2586-8ghr-69fj",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/rails/rails/security/advisories/GHSA-2586-8ghr-69fj"
        },
        {
          "name": "https://github.com/rails/rails/commit/5bb5ec66ed8faaf590ffe1222d7a5eb6e9d050f5",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/commit/5bb5ec66ed8faaf590ffe1222d7a5eb6e9d050f5"
        },
        {
          "name": "https://github.com/rails/rails/commit/d479192cf88a8b30a335a8bc25188a2d8e0f8d9f",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/commit/d479192cf88a8b30a335a8bc25188a2d8e0f8d9f"
        },
        {
          "name": "https://github.com/rails/rails/releases/tag/v8.0.5.2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/releases/tag/v8.0.5.2"
        },
        {
          "name": "https://github.com/rails/rails/releases/tag/v8.1.4.1",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails/releases/tag/v8.1.4.1"
        }
      ],
      "source": {
        "advisory": "GHSA-2586-8ghr-69fj",
        "discovery": "UNKNOWN"
      },
      "title": "Action Pack: Possible restoration of destroyed sessions in Action Dispatch CacheStore"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-126076",
    "datePublished": "2026-11-10T20:57:07.582Z",
    "dateReserved": "2026-11-10T17:07:43.285Z",
    "dateUpdated": "2026-11-12T19:05:13.367Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Mitigation
Implementation

Set sessions/credentials expiration date.

No CAPEC attack patterns related to this CWE.