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

Vulnerability from cvelistv5 – Published: 2026-11-16 08:36 – Updated: 2026-11-16 14:55
VLAI
Title
vulnerability-lookup: Feed key or API key authentication creates full web session bypassing password and 2FA
Summary
In the vulnerability-lookup web application, the authentication decorators for feed-key requests (auth_feedkey_func in website/decorators.py) and API-key requests (auth_func in website/web/api/v1/common.py) called Flask-Login's login_user() function. This caused the HTTP response to a request authenticated solely by a feed key (supplied as the X-FEED-KEY URL parameter) or an API key (supplied as the X-API-KEY header) to set a session cookie that grants full authenticated access to every page in the application, without requiring a password or two-factor authentication. The practical impact is that any party possessing a leaked feed URL (a common occurrence, as feed URLs are shared with RSS readers) or an API key could obtain a valid web session for the associated account. This session provides access to the user's account page, which exposes the API key and other profile data, and for accounts with the administrator role, access to the /admin interface, enabling full administrative control of the application. The vulnerability affects all users whose feed key or API key is exposed. No prior authentication, user interaction, or special network conditions are required; a single HTTP request with the token is sufficient to establish the session. The session persists until it expires, and because it is not bound to the original credential (a related CWE-613 issue noted by the developers), revoking the feed key or API key does not invalidate the already-created session. The fix replaces the login_user() call with assignment to g._login_user, which Flask-Login's current_user property reads for the current request only, without writing any session cookie. The affected views remain unchanged and continue to see the authenticated user for the single request.
SSVC
Exploitation: none Automatable: yes Technical Impact: total
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-16 08:23 UTC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 14:55 UTC
CWE
  • CWE-287 - Improper Authentication
  • CWE-613 - Insufficient Session Expiration
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 91/100 over 255 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
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",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-129703",
      "date": "2026-11-16",
      "epss": "0.00312",
      "percentile": "0.24454"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "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"
                  }
                ]
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8"
          }
        ],
        "cveTags": [],
        "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."
          }
        ],
        "id": "CVE-2026-129703",
        "lastModified": "2026-11-16T15:17:21.820",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "NONE",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "NOT_DEFINED",
                "integrityRequirement": "NOT_DEFINED",
                "modifiedAttackComplexity": "NOT_DEFINED",
                "modifiedAttackRequirements": "NOT_DEFINED",
                "modifiedAttackVector": "NOT_DEFINED",
                "modifiedPrivilegesRequired": "NOT_DEFINED",
                "modifiedSubAvailabilityImpact": "NOT_DEFINED",
                "modifiedSubConfidentialityImpact": "NOT_DEFINED",
                "modifiedSubIntegrityImpact": "NOT_DEFINED",
                "modifiedUserInteraction": "NOT_DEFINED",
                "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
                "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
                "modifiedVulnIntegrityImpact": "NOT_DEFINED",
                "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
              "ssvcData": {
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "total"
                  }
                ],
                "role": "Supplier",
                "timestamp": "2026-11-16T08:23:33Z",
                "version": "2.0.3"
              }
            },
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-129703",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "yes"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T14:55:15.356568Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-16T09:17:13.293",
        "references": [
          {
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "url": "https://github.com/vulnerability-lookup/vulnerability-lookup/commit/3605d5b65d340343cc4b612d40d454afed84302b"
          }
        ],
        "sourceIdentifier": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-287"
              },
              {
                "lang": "en",
                "value": "CWE-613"
              }
            ],
            "source": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
            "type": "Secondary"
          }
        ]
      }
    },
    "vulnrichment": {
      "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:20.394Z",
              "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"
    }
  }
}


Solutions

CNA · CIRCL
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.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.