Common Weakness Enumeration

CWE-362

Weakness Allowed-with-Review

Concurrent Execution using Shared Resource with Improper Synchronization

Abstraction: Class · Status: Draft

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

Technical nuance

A race condition violates these properties, which are closely related:

Exclusivity: the code sequence is given exclusive access to the shared resource, i.e., no other code sequence can modify properties of the shared resource before the original sequence has completed execution.

Atomicity: the code sequence is behaviorally atomic, i.e., no other thread or process can concurrently execute the same sequence of instructions (or a subset) against the same resource.

A race condition exists when an "interfering code sequence" can still access the shared resource, violating exclusivity.

The interfering code sequence could be "trusted" or "untrusted." A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.

Mapping guidance

This CWE entry is a Class and might have Base-level children that would be more appropriate

Examine children of this entry to see if there is a better fit

Relationships and members
ChildOf: CWE-662 · View CWE-1000
CanPrecede: CWE-416 · View CWE-1000
CanPrecede: CWE-476 · View CWE-1000
Modes of introduction
Architecture and Design
Implementation

Programmers may assume that certain code sequences execute too quickly to be affected by an interfering code sequence; when they are not, this violates atomicity. For example, the single "x++" statement may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read (the original value of x), followed by a computation (x+1), followed by a write (save the result to x).

Detection methods

Black Box

Black box methods may be able to identify evidence of race conditions via methods such as multiple simultaneous connections, which may cause the software to become instable or crash. However, race conditions with very narrow timing windows would not be detectable.

White Box

Common idioms are detectable in white box analysis, such as time-of-check-time-of-use (TOCTOU) file operations (CWE-367), or double-checked locking (CWE-609).

Automated Dynamic Analysis

This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results.

Race conditions may be detected with a stress-test by calling the software simultaneously from a large number of threads or processes, and look for evidence of any unexpected behavior.

Insert breakpoints or delays in between relevant code statements to artificially expand the race window so that it will be easier to detect.

Effectiveness: Moderate

Automated Static Analysis - Binary or Bytecode

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Bytecode Weakness Analysis - including disassembler + source code weakness analysis

Cost effective for partial coverage:

Binary Weakness Analysis - including disassembler + source code weakness analysis

Effectiveness: High

Dynamic Analysis with Automated Results Interpretation

According to SOAR [REF-1479], the following detection techniques may be useful:

Cost effective for partial coverage:

Web Application Scanner

Web Services Scanner

Database Scanners

Effectiveness: SOAR Partial

Dynamic Analysis with Manual Results Interpretation

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Framework-based Fuzzer

Cost effective for partial coverage:

Fuzz Tester

Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious

Effectiveness: High

Manual Static Analysis - Source Code

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Manual Source Code Review (not inspections)

Cost effective for partial coverage:

Focused Manual Spotcheck - Focused manual analysis of source

Effectiveness: High

Automated Static Analysis - Source Code

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Source code Weakness Analyzer

Context-configured Source Code Weakness Analyzer

Effectiveness: High

Architecture or Design Review

According to SOAR [REF-1479], the following detection techniques may be useful:

Highly cost effective:

Formal Methods / Correct-By-Construction

Cost effective for partial coverage:

Inspection (IEEE 1028 standard) (can apply to requirements, design, source code, etc.)

Effectiveness: High

Notes

Maintenance

The relationship between race conditions and synchronization problems (CWE-662) needs to be further developed. They are not necessarily two perspectives of the same core concept, since synchronization is only one technique for avoiding race conditions, and synchronization can be used for other purposes besides race condition prevention.

Research Gap

Race conditions in web applications are under-studied and probably under-reported. However, in 2008 there has been growing interest in this area.

Research Gap

Much of the focus of race condition research has been in Time-of-check Time-of-use (TOCTOU) variants (CWE-367), but many race conditions are related to synchronization problems that do not necessarily require a time-of-check.

Research Gap

From a classification/taxonomy perspective, the relationships between concurrency and program state need closer investigation and may be useful in organizing related issues.

Content history
Submission: PLOVER · 2006-07-19 · CWE Draft 3
Contribution: Martin Sebor · Cisco Systems, Inc. · 2010-04-30 · CWE 1.13

Provided Demonstrative Example

Contribution: Abhi Balakrishnan · 2024-02-29 · CWE 4.16

Provided diagram to improve CWE usability

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

updated Time_of_Introduction

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

updated Relationships, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2008-10-14 · CWE 1.0.1

updated Relationships

Modification: CWE Content Team · MITRE · 2008-11-24 · CWE 1.1

updated Relationships, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2009-01-12 · CWE 1.2

updated Applicable_Platforms, Common_Consequences, Demonstrative_Examples, Description, Likelihood_of_Exploit, Maintenance_Notes, Observed_Examples, Potential_Mitigations, References, Relationships, Research_Gaps

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

updated Demonstrative_Examples, Potential_Mitigations

Modification: CWE Content Team · MITRE · 2009-05-27 · CWE 1.4

updated Relationships

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

updated Detection_Factors, References, Relationships

Modification: CWE Content Team · MITRE · 2010-06-21 · CWE 1.9

updated Common_Consequences, Demonstrative_Examples, Detection_Factors, Potential_Mitigations, References

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

updated Observed_Examples, Potential_Mitigations, Relationships

Modification: CWE Content Team · MITRE · 2010-12-13 · CWE 1.11

updated Applicable_Platforms, Demonstrative_Examples, Description, Name, Potential_Mitigations, Relationships

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

updated Common_Consequences, Relationships, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2011-06-27 · CWE 2.0

updated Relationships

Modification: CWE Content Team · MITRE · 2011-09-13 · CWE 2.1

updated Relationships, Taxonomy_Mappings

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

updated Potential_Mitigations, References, Relationships

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

updated Detection_Factors, Relationships

Modification: CWE Content Team · MITRE · 2015-12-07 · CWE 2.9

updated Relationships

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

updated Demonstrative_Examples, References, Research_Gaps, Taxonomy_Mappings

Modification: CWE Content Team · MITRE · 2019-01-03 · CWE 3.2

updated Relationships, Taxonomy_Mappings

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

updated Relationships

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

updated Applicable_Platforms, Demonstrative_Examples, Observed_Examples, Relationships

Modification: CWE Content Team · MITRE · 2020-08-20 · CWE 4.2

updated Relationships

Modification: CWE Content Team · MITRE · 2021-03-15 · CWE 4.4

updated Demonstrative_Examples

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

updated Observed_Examples, References

Modification: CWE Content Team · MITRE · 2022-04-28 · CWE 4.7

updated Observed_Examples, Relationships

Modification: CWE Content Team · MITRE · 2022-06-28 · CWE 4.8

updated Observed_Examples, Relationships

Modification: CWE Content Team · MITRE · 2022-10-13 · CWE 4.9

updated Observed_Examples, References

Modification: CWE Content Team · MITRE · 2023-01-31 · CWE 4.10

updated Applicable_Platforms, Common_Consequences, Description

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

updated References, Relationships

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

updated Mapping_Notes, Relationships

Modification: CWE Content Team · MITRE · 2024-07-16 · CWE 4.15

updated Relationships

Modification: CWE Content Team · MITRE · 2024-11-19 · CWE 4.16

updated Alternate_Terms, Common_Consequences, Description, Diagram, Modes_of_Introduction

Modification: CWE Content Team · MITRE · 2025-04-03 · CWE 4.17

updated Affected_Resources

Modification: CWE Content Team · MITRE · 2025-09-09 · CWE 4.18

updated Detection_Factors, References

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

updated Observed_Examples, Relationships, Weakness_Ordinalities

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

updated Observed_Examples

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

updated Applicable_Platforms, Background_Details, Demonstrative_Examples, Description, Name, Observed_Examples, References, Relationships, Taxonomy_Mappings, Technical_Nuance

3802 vulnerabilities reference this CWE, most recent first.

CVE-2026-134321 (GCVE-0-2026-134321)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
better-auth before 1.7.16 Session Revocation Bypass via Secondary Storage and Cookie Cache
Summary
better-auth from 0.8.1-beta.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and @better-auth/passkey from 1.6.25 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, let revoked sessions stay valid because secondary storage session lists are updated non-atomically and some routes trust cookie-cached sessions. An attacker holding a valid session can evade bulk revocation or bans, or use a revoked cached session to register a passkey or create a lasting session.
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
better-auth better-auth Affected: 0.8.1-beta.5 , < 1.7.16 (semver)
Unaffected: 1.7.16 (semver)
Create a notification for this product.
better-auth better-auth Affected: 1.8.0-beta.0 , < 1.8.0-beta.5 (semver)
Unaffected: 1.8.0-beta.5 (semver)
Create a notification for this product.
better-auth better-auth Affected: 1.6.25 , < 1.7.16 (semver)
Unaffected: 1.7.16 (semver)
Create a notification for this product.
Date Public
2026-11-03 00:00
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/better-auth",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.7.16",
              "status": "affected",
              "version": "0.8.1-beta.5",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.7.16",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/better-auth",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.8.0-beta.5",
              "status": "affected",
              "version": "1.8.0-beta.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.8.0-beta.5",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/passkey",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.7.16",
              "status": "affected",
              "version": "1.6.25",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.7.16",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/passkey",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.8.0-beta.5",
              "status": "affected",
              "version": "1.8.0-beta.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.8.0-beta.5",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:better-auth:better_auth:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.7.16",
                  "versionStartIncluding": "0.8.1-beta.5",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        },
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:better-auth:better_auth:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.8.0-beta.5",
                  "versionStartIncluding": "1.8.0-beta.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "kumama-nui"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "5255fgh"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "ebadfd"
        }
      ],
      "datePublic": "2026-11-03T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "better-auth from 0.8.1-beta.5 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, and @better-auth/passkey from 1.6.25 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5, let revoked sessions stay valid because secondary storage session lists are updated non-atomically and some routes trust cookie-cached sessions. An attacker holding a valid session can evade bulk revocation or bans, or use a revoked cached session to register a passkey or create a lasting session."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "PASSIVE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC: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": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:48.347Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-fvxx-76fc-893x)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/better-auth/better-auth/security/advisories/GHSA-fvxx-76fc-893x"
        },
        {
          "name": "VulnCheck Advisory: better-auth before 1.7.16 Session Revocation Bypass via Secondary Storage and Cookie Cache",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/better-auth-before-1.7.16-session-revocation-bypass-via-secondary-storage-and-cookie-cache"
        }
      ],
      "title": "better-auth before 1.7.16 Session Revocation Bypass via Secondary Storage and Cookie Cache",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134321",
    "datePublished": "2026-11-21T16:34:48.347Z",
    "dateReserved": "2026-11-20T23:53:36.035Z",
    "dateUpdated": "2026-11-21T16:34:48.347Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-134313 (GCVE-0-2026-134313)

Vulnerability from cvelistv5 – Published: 2026-11-21 16:34 – Updated: 2026-11-21 16:34
VLAI
Title
Better Auth before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 Session Mix-Up via MySQL Serial IDs
Summary
Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition with MySQL or MariaDB serial IDs because the inserted row's ID is read via a separate LAST_INSERT_ID() query that may run on a different pooled connection. Under concurrent load, a user signing in can receive another user's session and act as that user.
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
better-auth kysely-adapter Affected: 1.5.0-beta.9 , < 1.7.16 (semver)
Unaffected: 1.7.16 (semver)
Create a notification for this product.
better-auth kysely-adapter Affected: 1.8.0-beta.0 , < 1.8.0-beta.5 (semver)
Unaffected: 1.8.0-beta.5 (semver)
Create a notification for this product.
better-auth drizzle-adapter Affected: 1.5.0-beta.9 , < 1.7.16 (semver)
Unaffected: 1.7.16 (semver)
Create a notification for this product.
better-auth drizzle-adapter Affected: 1.8.0-beta.0 , < 1.8.0-beta.5 (semver)
Unaffected: 1.8.0-beta.5 (semver)
Create a notification for this product.
better-auth better-auth Affected: 0 , < 1.7.16 (semver)
Unaffected: 1.7.16 (semver)
Create a notification for this product.
better-auth better-auth Affected: 1.8.0-beta.0 , < 1.8.0-beta.5 (semver)
Unaffected: 1.8.0-beta.5 (semver)
Create a notification for this product.
Date Public
2026-11-03 00:00
Credits
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/kysely-adapter",
          "product": "kysely-adapter",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.7.16",
              "status": "affected",
              "version": "1.5.0-beta.9",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.7.16",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/kysely-adapter",
          "product": "kysely-adapter",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.8.0-beta.5",
              "status": "affected",
              "version": "1.8.0-beta.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.8.0-beta.5",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/drizzle-adapter",
          "product": "drizzle-adapter",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.7.16",
              "status": "affected",
              "version": "1.5.0-beta.9",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.7.16",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/%40better-auth/drizzle-adapter",
          "product": "drizzle-adapter",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.8.0-beta.5",
              "status": "affected",
              "version": "1.8.0-beta.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.8.0-beta.5",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/better-auth",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.7.16",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.7.16",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "packageURL": "pkg:npm/better-auth",
          "product": "better-auth",
          "vendor": "better-auth",
          "versions": [
            {
              "lessThan": "1.8.0-beta.5",
              "status": "affected",
              "version": "1.8.0-beta.0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "1.8.0-beta.5",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:better-auth:better_auth:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.7.16",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        },
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:better-auth:better_auth:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "1.8.0-beta.5",
                  "versionStartIncluding": "1.8.0-beta.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "wrufeger"
        }
      ],
      "datePublic": "2026-11-03T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "Better Auth (better-auth, @better-auth/kysely-adapter, and @better-auth/drizzle-adapter) before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains a race condition with MySQL or MariaDB serial IDs because the inserted row\u0027s ID is read via a separate LAST_INSERT_ID() query that may run on a different pooled connection. Under concurrent load, a user signing in can receive another user\u0027s session and act as that user."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 7.6,
            "baseSeverity": "HIGH",
            "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:H/VI:H/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 6.8,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-21T16:34:55.987Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-48c2-w96j-mv3m)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/better-auth/better-auth/security/advisories/GHSA-48c2-w96j-mv3m"
        },
        {
          "name": "VulnCheck Advisory: Better Auth before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 Session Mix-Up via MySQL Serial IDs",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/better-auth-before-1.7.16-and-1.8.0-beta.0-before-1.8.0-beta.5-session-mix-up-via-mysql-serial-ids"
        }
      ],
      "title": "Better Auth before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 Session Mix-Up via MySQL Serial IDs",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-134313",
    "datePublished": "2026-11-21T16:34:55.987Z",
    "dateReserved": "2026-11-20T23:52:03.518Z",
    "dateUpdated": "2026-11-21T16:34:55.987Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-133851 (GCVE-0-2026-133851)

Vulnerability from cvelistv5 – Published: 2026-11-20 14:40 – Updated: 2026-11-20 16:34
VLAI
Title
FlowIntel Alerting: Missing Private Case Authorization Check Allows Connector Owners to Access Revoked Case Data
Summary
FlowIntel's alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case. This meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case. Additionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case. Impact: - Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints. - Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access. - Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races. Affected versions: FlowIntel prior to 4.1.0.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
Supplier · CIRCL (v2.0.3)
Decision recorded 2026-11-20 14:20 UTC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-20 16:22 UTC
CWE
  • CWE-862 - Missing Authorization
  • CWE-362 - Concurrent Execution using Shared Resource with Inadequate Locking
Assigner
CIRCL CNA under the ENISA root
CNA scorecard A 92/100 over 310 records in the last 180 days details
References
Impacted products
Vendor Product Version
flowintel flowintel Affected: 0 , < 4.1.0 (semver)
    cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*
Create a notification for this product.
GCVE extensions
bcp-05-x-01
AI-assisted vulnerability information annotation
GCVE-BCP-05-X-01
Whole record AI-generated Human-reviewed GNA-1

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

ai-computer-assisted:llm-generatedai-computer-assisted:classification
Model Source Identifier
qwen3.8:27b ollama qwen3.8:27b
bcp-05-x-02
Patch-to-vulnerability generation provenance
GCVE-BCP-05-X-02
Generator
patch2vuln.py on 2026-11-20 14:20
Model
qwen3.8:27b
Input
https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff e8226318f1d6…
Confidence
medium
Commit Subject Patch SHA-256
68d85c78e464 fix: [security] Enforce private case access for alert reviews e8226318f1d6…
Fix summary

The fix enforces private case visibility as a mandatory gate before any connector-ownership check can grant alert access. If an alert is linked to a private case and the user cannot view that case, access is denied regardless of ownership. A post-commit re-verification is added after review-status updates and after detecting a competing case-creation claim, ensuring that concurrent association changes do not result in unauthorized data disclosure in the response.

Patch summary

In can_user_view_alert, the private-case membership check was moved before the connector-ownership checks and made unconditional (no longer gated on case.is_private), so any user lacking case access is denied even if they own the connector. In update_review_status, a can_user_view_alert re-check is performed after the database commit and before returning the serialized alert, returning 403 if access was concurrently lost. In create_case_from_alert, after a competing claim is detected, a can_user_view_alert re-check gates the response that would otherwise return the winner's case_id. The unused import get_present_in_case was removed. 33 regression tests were added covering revoked access, connector scope, concurrent case-link transitions, and authorized-user preservation.

CVSS rationale

AV:N: The vulnerability is exploitable over the network via the FlowIntel web API. AC:L: No special race condition or complex setup is required; a connector owner whose case access was revoked can simply call the alert endpoints. AT:N: No manipulation of the target is needed. PR:L: The attacker must be an authenticated user with connector ownership of the alert. UI:N: No victim interaction is required. VC:L: Confidential impact is limited to alert-level data (review comments, raw payload, action history) rather than full case contents. VI:L: The attacker can modify review status and create cases, but cannot alter case data directly. VA:N: No availability impact. SC/SI/SA:N: No impact on other systems.

Weakness rationale
  • CWE-862 The alert access function did not verify private case membership before granting access based on connector ownership. The authorization check for case-level access was either absent or insufficiently ordered, allowing a user with connector ownership to bypass the private case boundary.
  • CWE-362 The review-status update and case-creation paths did not re-verify authorization after the database commit, creating a TOCTOU window where a concurrent session could link the alert to a private case and the response would still disclose case data to an unauthorized user.
Attack pattern rationale
  • CAPEC-114 The attacker directly requests alert API endpoints (review, case-creation, read) using a known alert identifier. Because the authorization logic did not enforce private case membership, the server returned sensitive case data and accepted state-changing actions. This is the closest CAPEC to the observed pattern of accessing a resource by directly specifying its identifier without the required authorization context. Uncertainty: the attack does not involve guessing URLs but rather exploiting a logic flaw in an existing authorized endpoint; however, CAPEC-114 remains the best available match for direct resource access bypassing intended access controls.
Assumptions to verify
  • The affected version range is inferred from the explicit context (affected_version '0', fixed_version '4.1.0'); no explicit changelog or release notes are available to confirm the exact first vulnerable release.
  • The CAPEC-114 mapping is the closest available pattern; the actual attack is a logic flaw in authorization ordering rather than classic forced browsing, but no more specific CAPEC exists for missing authorization checks in API endpoints.
  • CVSS PR:L assumes the attacker must be an authenticated user with connector ownership; if the product allows unauthenticated access to alert endpoints, PR would be N, but the patch evidence (session-based auth, API keys in tests) supports authenticated access.
  • The TOCTOU component (CWE-362) requires a concurrent session to link the alert to a private case at the precise moment of the response; this is a secondary vector and the primary issue is the missing authorization check (CWE-862).
  • The commit message references 'Tool: Codex' which is noted as the AI tool used to assist in development; no credit is assigned for this as it is not a person or organization.
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 7 11 medium 5
bcp-05-x-03
Vulnerability handling and disclosure timeline
GCVE-BCP-05-X-03
  1. 2026-11-17 09:50 UTC Fix developed Corrective change authored (68d85c78e464f023f9f77af9af39634d3b811fff): fix: [security] Enforce private case access for alert reviews https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff
  2. 2026-11-20 14:20 UTC Fix available Patch retrieved from the supplied URL; retrieval time is used as the default availability time. https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-133851",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-20T16:22:03.525644Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-20T16:34:09.703Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "app/alerting/alerting_core.py"
          ],
          "product": "flowintel",
          "programFiles": [
            "app/alerting/alerting_core.py"
          ],
          "repo": "https://github.com/flowintel/flowintel",
          "vendor": "flowintel",
          "versions": [
            {
              "lessThan": "4.1.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "David Cruciani"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "FlowIntel\u0027s alerting module contained an authorization bypass in the alert access control logic. When an alert was linked to a private case, the system relied solely on connector ownership (user or organization) to determine access, without verifying that the requesting user still held valid membership in the associated private case.\n\nThis meant that a user who was a connector owner of an alert could continue to read alert details, review history, raw payloads, and action comments, and could perform review-status updates or case-creation actions, even after their access to the linked private case had been revoked or they were never a member of that case.\n\nAdditionally, a time-of-check to time-of-use (TOCTOU) gap existed: after a review-status update or a competing case-creation claim was committed, the response could disclose private case identifiers or review history to a user whose access had been concurrently removed by another session linking the alert to a private case.\n\nImpact:\n- Unauthorized disclosure of private case data (review comments, raw payloads, action history) through alert endpoints.\n- Unauthorized modification of alert review status and creation of cases from alerts the user should no longer access.\n- Leakage of a competing case identifier to an unauthorized user during concurrent case-creation races.\n\nAffected versions: FlowIntel prior to 4.1.0."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-114",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-114 Forced Browsing"
            }
          ]
        }
      ],
      "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:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "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-20T14:20:59Z",
              "version": "2.0.3"
            },
            "type": "SSVC"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-862",
              "description": "CWE-862 Missing Authorization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "CWE-362 Concurrent Execution using Shared Resource with Inadequate Locking",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-20T14:40:10.021Z",
        "orgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
        "shortName": "CIRCL"
      },
      "references": [
        {
          "name": "Security patch",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "The fix enforces private case visibility as a mandatory gate before any connector-ownership check can grant alert access. If an alert is linked to a private case and the user cannot view that case, access is denied regardless of ownership. A post-commit re-verification is added after review-status updates and after detecting a competing case-creation claim, ensuring that concurrent association changes do not result in unauthorized data disclosure in the response."
        }
      ],
      "title": "FlowIntel Alerting: Missing Private Case Authorization Check Allows Connector Owners to Access Revoked Case Data",
      "x_gcve": [
        {
          "extensions": {
            "bcp-05-x-01": {
              "ai_annotations": [
                {
                  "ai_level": "generated",
                  "description": "Draft vulnerability metadata was generated from a git-format patch using an Ollama-hosted language model. Human validation is required before publication.",
                  "gna_source": 1,
                  "models": [
                    {
                      "gna_source": 1,
                      "identifier": "qwen3.8:27b",
                      "name": "qwen3.8:27b",
                      "source": "ollama"
                    }
                  ],
                  "review_status": "full",
                  "scope": "record",
                  "tags": [
                    "ai-computer-assisted:llm-generated",
                    "ai-computer-assisted:classification"
                  ]
                }
              ]
            },
            "bcp-05-x-02": {
              "x_patch2vuln": {
                "assumptions": [
                  "The affected version range is inferred from the explicit context (affected_version \u00270\u0027, fixed_version \u00274.1.0\u0027); no explicit changelog or release notes are available to confirm the exact first vulnerable release.",
                  "The CAPEC-114 mapping is the closest available pattern; the actual attack is a logic flaw in authorization ordering rather than classic forced browsing, but no more specific CAPEC exists for missing authorization checks in API endpoints.",
                  "CVSS PR:L assumes the attacker must be an authenticated user with connector ownership; if the product allows unauthenticated access to alert endpoints, PR would be N, but the patch evidence (session-based auth, API keys in tests) supports authenticated access.",
                  "The TOCTOU component (CWE-362) requires a concurrent session to link the alert to a private case at the precise moment of the response; this is a secondary vector and the primary issue is the missing authorization check (CWE-862).",
                  "The commit message references \u0027Tool: Codex\u0027 which is noted as the AI tool used to assist in development; no credit is assigned for this as it is not a person or organization."
                ],
                "capecRationale": [
                  {
                    "capecId": "CAPEC-114",
                    "rationale": "The attacker directly requests alert API endpoints (review, case-creation, read) using a known alert identifier. Because the authorization logic did not enforce private case membership, the server returned sensitive case data and accepted state-changing actions. This is the closest CAPEC to the observed pattern of accessing a resource by directly specifying its identifier without the required authorization context. Uncertainty: the attack does not involve guessing URLs but rather exploiting a logic flaw in an existing authorized endpoint; however, CAPEC-114 remains the best available match for direct resource access bypassing intended access controls."
                  }
                ],
                "commit": "68d85c78e464f023f9f77af9af39634d3b811fff",
                "confidence": "medium",
                "credits": [
                  {
                    "lang": "en",
                    "type": "remediation developer",
                    "value": "David Cruciani"
                  }
                ],
                "cvssRationale": "AV:N: The vulnerability is exploitable over the network via the FlowIntel web API. AC:L: No special race condition or complex setup is required; a connector owner whose case access was revoked can simply call the alert endpoints. AT:N: No manipulation of the target is needed. PR:L: The attacker must be an authenticated user with connector ownership of the alert. UI:N: No victim interaction is required. VC:L: Confidential impact is limited to alert-level data (review comments, raw payload, action history) rather than full case contents. VI:L: The attacker can modify review status and create cases, but cannot alter case data directly. VA:N: No availability impact. SC/SI/SA:N: No impact on other systems.",
                "fixSummary": "The fix enforces private case visibility as a mandatory gate before any connector-ownership check can grant alert access. If an alert is linked to a private case and the user cannot view that case, access is denied regardless of ownership. A post-commit re-verification is added after review-status updates and after detecting a competing case-creation claim, ensuring that concurrent association changes do not result in unauthorized data disclosure in the response.",
                "generatedAt": "2026-11-20T14:20:59.693658Z",
                "generator": "patch2vuln.py",
                "model": "qwen3.8:27b",
                "modelComparison": {
                  "potentialErrors": [],
                  "rankings": [
                    {
                      "agreementScore": 11,
                      "assumptionCount": 5,
                      "confidence": "medium",
                      "model": "qwen3.8:27b",
                      "score": 7
                    }
                  ],
                  "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": "e8226318f1d6462435435a1293e4a5091a59c7cd5671dbd98013ff3ae14d856a",
                "patchSummary": "In can_user_view_alert, the private-case membership check was moved before the connector-ownership checks and made unconditional (no longer gated on case.is_private), so any user lacking case access is denied even if they own the connector. In update_review_status, a can_user_view_alert re-check is performed after the database commit and before returning the serialized alert, returning 403 if access was concurrently lost. In create_case_from_alert, after a competing claim is detected, a can_user_view_alert re-check gates the response that would otherwise return the winner\u0027s case_id. The unused import get_present_in_case was removed. 33 regression tests were added covering revoked access, connector scope, concurrent case-link transitions, and authorized-user preservation.",
                "patchTruncated": false,
                "patches": [
                  {
                    "commit": "68d85c78e464f023f9f77af9af39634d3b811fff",
                    "date": "Tue, 17 Nov 2026 10:50:38 +0100",
                    "patchSha256": "e8226318f1d6462435435a1293e4a5091a59c7cd5671dbd98013ff3ae14d856a",
                    "retrievedAt": "2026-11-20T14:20:26.159139Z",
                    "source": "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff",
                    "sourceUrl": "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff",
                    "subject": "fix: [security] Enforce private case access for alert reviews"
                  }
                ],
                "source": "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff",
                "ssvc": {
                  "options": [
                    {
                      "Exploitation": "none"
                    },
                    {
                      "Automatable": "yes"
                    },
                    {
                      "Technical Impact": "partial"
                    }
                  ],
                  "role": "Supplier",
                  "timestamp": "2026-11-20T14:20:59Z",
                  "version": "2.0.3"
                },
                "subject": "fix: [security] Enforce private case access for alert reviews",
                "weaknessRationale": [
                  {
                    "cweId": "CWE-862",
                    "rationale": "The alert access function did not verify private case membership before granting access based on connector ownership. The authorization check for case-level access was either absent or insufficiently ordered, allowing a user with connector ownership to bypass the private case boundary."
                  },
                  {
                    "cweId": "CWE-362",
                    "rationale": "The review-status update and case-creation paths did not re-verify authorization after the database commit, creating a TOCTOU window where a concurrent session could link the alert to a private case and the response would still disclose case data to an unauthorized user."
                  }
                ]
              }
            },
            "bcp-05-x-03": {
              "x_timeline": {
                "events": [
                  {
                    "description": "Corrective change authored (68d85c78e464f023f9f77af9af39634d3b811fff): fix: [security] Enforce private case access for alert reviews",
                    "id": "evt-fix-developed-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"
                    ],
                    "timestamp": "2026-11-17T09:50:38Z",
                    "type": "fix-developed"
                  },
                  {
                    "description": "Patch retrieved from the supplied URL; retrieval time is used as the default availability time.",
                    "id": "evt-fix-available-1",
                    "references": [
                      "https://github.com/flowintel/flowintel/commit/68d85c78e464f023f9f77af9af39634d3b811fff"
                    ],
                    "timestamp": "2026-11-20T14:20:26.159139Z",
                    "type": "fix-available"
                  }
                ]
              }
            }
          },
          "recordType": "advisory",
          "vulnId": "GCVE-1-2026-20419"
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "5a6e4751-2f3f-4070-9419-94fb35b644e8",
    "assignerShortName": "CIRCL",
    "cveId": "CVE-2026-133851",
    "datePublished": "2026-11-20T14:40:10.021Z",
    "dateReserved": "2026-11-20T14:40:00.274Z",
    "dateUpdated": "2026-11-20T16:34:09.703Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-132043 (GCVE-0-2026-132043)

Vulnerability from cvelistv5 – Published: 2026-11-19 09:01 – Updated: 2026-11-19 15:07
VLAI
Title
Concurrent formatted-number parsing can return another caller's value
Summary
In Eclipse Yasson versions 3.0 to 3.0.5, a race condition (CWE-362) exists in the handling of @JsonbNumberFormat. Yasson creates one java.text.NumberFormat instance per annotated property and shares it across all threads that use the same Jsonb instance. NumberFormat is not thread-safe, and the deserializer called parse() on it without synchronization. When multiple threads deserialize concurrently, a thread can receive a numeric value that belongs to another thread's input, receive an incorrect value, or fail with an exception. A remote attacker who can send concurrent requests to an application that deserializes untrusted JSON this way may cause incorrect data to be processed or cause another user's value to be returned. Exploitation requires that the application use @JsonbNumberFormat with a shared Jsonb instance and that the attacker win a timing race. This issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances.
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-19 15:06 UTC
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization
Assigner
eclipse CNA under the mitre root
CNA scorecard C 66/100 over 238 records in the last 180 days details
Impacted products
Vendor Product Version
Eclipse Foundation Eclipse Yasson Affected: 3.0 , ≤ 3.0.5 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-132043",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-19T15:06:40.712481Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-19T15:07:01.217Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1356"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Eclipse Yasson",
          "vendor": "Eclipse Foundation",
          "versions": [
            {
              "lessThanOrEqual": "3.0.5",
              "status": "affected",
              "version": "3.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Patrick Schaub"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eIn Eclipse Yasson versions 3.0 to 3.0.5, a race condition (CWE-362) exists in the handling of @JsonbNumberFormat. Yasson creates one java.text.NumberFormat instance per annotated property and shares it across all threads that use the same Jsonb instance. NumberFormat is not thread-safe, and the deserializer called parse() on it without synchronization. When multiple threads deserialize concurrently, a thread can receive a numeric value that belongs to another thread\u0027s input, receive an incorrect value, or fail with an exception. A remote attacker who can send concurrent requests to an application that deserializes untrusted JSON this way may cause incorrect data to be processed or cause another user\u0027s value to be returned. Exploitation requires that the application use @JsonbNumberFormat with a shared Jsonb instance and that the attacker win a timing race. This issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances.\u003c/p\u003e"
            }
          ],
          "value": "In Eclipse Yasson versions 3.0 to 3.0.5, a race condition (CWE-362) exists in the handling of @JsonbNumberFormat. Yasson creates one java.text.NumberFormat instance per annotated property and shares it across all threads that use the same Jsonb instance. NumberFormat is not thread-safe, and the deserializer called parse() on it without synchronization. When multiple threads deserialize concurrently, a thread can receive a numeric value that belongs to another thread\u0027s input, receive an incorrect value, or fail with an exception. A remote attacker who can send concurrent requests to an application that deserializes untrusted JSON this way may cause incorrect data to be processed or cause another user\u0027s value to be returned. Exploitation requires that the application use @JsonbNumberFormat with a shared Jsonb instance and that the attacker win a timing race. This issue is fixed in version 3.0.6 by synchronizing access to the shared NumberFormat instances."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-26",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-26 Leveraging Race Conditions"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "NONE",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-19T09:01:17.406Z",
        "orgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
        "shortName": "eclipse"
      },
      "references": [
        {
          "url": "https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/1356"
        },
        {
          "url": "https://gitlab.eclipse.org/security/cve-assignment/-/work_items/603"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Concurrent formatted-number parsing can return another caller\u0027s value",
      "x_generator": {
        "engine": "Vulnogram 1.0.5"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "e51fbebd-6053-4e49-959f-1b94eeb69a2c",
    "assignerShortName": "eclipse",
    "cveId": "CVE-2026-132043",
    "datePublished": "2026-11-19T09:01:17.406Z",
    "dateReserved": "2026-11-18T09:58:38.111Z",
    "dateUpdated": "2026-11-19T15:07:01.217Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-129356 (GCVE-0-2026-129356)

Vulnerability from cvelistv5 – Published: 2026-11-15 01:15 – Updated: 2026-11-16 15:37 X_Open Source
VLAI
Title
vllm-project vllm Common Prefix single_type_kv_cache_manager.py race condition
Summary
A vulnerability was found in vllm-project vllm 0.30.0/0.31.0. This vulnerability affects unknown code of the file single_type_kv_cache_manager.py of the component Common Prefix Handler. The manipulation results in race condition. The attack may be performed from remote. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been made public and could be used. Upgrading to version 0.32.0 is able to resolve this issue. The patch is identified as e687a251bb056fa527846633f7a1b0a6c0f42374. You should upgrade the affected component.
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-16 15:12 UTC
CWE
Assigner
VulDB CNA under the mitre root
CNA scorecard B 83/100 over 3776 records in the last 180 days details
Impacted products
Vendor Product Version
vllm-project vllm Affected: 0.30.0
Affected: 0.31.0
Unaffected: 0.32.0
    cpe:2.3:a:vllm-project:vllm:*:*:*:*:*:*:*:*
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-129356",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-16T15:12:04.729936Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-16T15:37:21.853Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "cpes": [
            "cpe:2.3:a:vllm-project:vllm:*:*:*:*:*:*:*:*"
          ],
          "modules": [
            "Common Prefix Handler"
          ],
          "product": "vllm",
          "vendor": "vllm-project",
          "versions": [
            {
              "status": "affected",
              "version": "0.30.0"
            },
            {
              "status": "affected",
              "version": "0.31.0"
            },
            {
              "status": "unaffected",
              "version": "0.32.0"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "Zyz3366 (VulDB User)"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "A vulnerability was found in vllm-project vllm 0.30.0/0.31.0. This vulnerability affects unknown code of the file single_type_kv_cache_manager.py of the component Common Prefix Handler. The manipulation results in race condition. The attack may be performed from remote. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been made public and could be used. Upgrading to version 0.32.0 is able to resolve this issue. The patch is identified as e687a251bb056fa527846633f7a1b0a6c0f42374. You should upgrade the affected component."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "baseScore": 2.3,
            "baseSeverity": "LOW",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P",
            "version": "4.0"
          }
        },
        {
          "cvssV3_1": {
            "baseScore": 5,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C",
            "version": "3.1"
          }
        },
        {
          "cvssV3_0": {
            "baseScore": 5,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:O/RC:C",
            "version": "3.0"
          }
        },
        {
          "cvssV2_0": {
            "baseScore": 4.6,
            "vectorString": "AV:N/AC:H/Au:S/C:P/I:P/A:P/E:POC/RL:OF/RC:C",
            "version": "2.0"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Race Condition",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-15T01:15:24.018Z",
        "orgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
        "shortName": "VulDB"
      },
      "references": [
        {
          "name": "VDB-437419 | vllm-project vllm Common Prefix single_type_kv_cache_manager.py race condition",
          "tags": [
            "vdb-entry"
          ],
          "url": "https://vuldb.com/vuln/437419"
        },
        {
          "name": "VDB-437419 | CTI Indicators (IOB, IOC, IOA)",
          "tags": [
            "signature",
            "permissions-required"
          ],
          "url": "https://vuldb.com/vuln/437419/cti"
        },
        {
          "name": "CVE-2026-129356 | CVE Analysis and Report",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/cve/CVE-2026-129356"
        },
        {
          "name": "Submit #1043823 | vLLM Project vLLM v0.30.0, v0.31.0 Improper Resource Management",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://vuldb.com/submit/1043823"
        },
        {
          "tags": [
            "exploit",
            "issue-tracking"
          ],
          "url": "https://github.com/vllm-project/vllm/issues/61673"
        },
        {
          "tags": [
            "issue-tracking",
            "patch"
          ],
          "url": "https://github.com/vllm-project/vllm/pull/61126"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/vllm-project/vllm/commit/e687a251bb056fa527846633f7a1b0a6c0f42374"
        },
        {
          "tags": [
            "patch"
          ],
          "url": "https://github.com/vllm-project/vllm/releases/tag/v0.32.0"
        },
        {
          "tags": [
            "product"
          ],
          "url": "https://github.com/vllm-project/vllm/"
        }
      ],
      "tags": [
        "x_open-source"
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-11-14T00:00:00.000Z",
          "value": "Advisory disclosed"
        },
        {
          "lang": "en",
          "time": "2026-11-14T01:00:00.000Z",
          "value": "VulDB entry created"
        },
        {
          "lang": "en",
          "time": "2026-11-14T07:47:52.000Z",
          "value": "VulDB entry last update"
        }
      ],
      "title": "vllm-project vllm Common Prefix single_type_kv_cache_manager.py race condition",
      "x_generator": [
        "VulDB PVTS v202611"
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "1af790b2-7ee1-4545-860a-a788eba489b5",
    "assignerShortName": "VulDB",
    "cveId": "CVE-2026-129356",
    "datePublished": "2026-11-15T01:15:24.018Z",
    "dateReserved": "2026-11-14T06:42:47.336Z",
    "dateUpdated": "2026-11-16T15:37:21.853Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128069 (GCVE-0-2026-128069)

Vulnerability from cvelistv5 – Published: 2026-11-13 17:17 – Updated: 2026-11-18 12:45
VLAI
Title
rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls
Summary
rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Before 1.7.2, the HTML4 and HTML5 variants of Rails::HTML::SafeListSanitizer reuse one Rails::HTML::PermitScrubber across calls and mutate its tags and attributes without synchronization. In a multithreaded process, concurrent sanitize calls using different tags: or attributes: options can interleave and cause one call to use the other call's allowlist. If a permissive call admits a script element or event-handler attribute, output expected to be sanitized under a stricter policy can retain it and cause cross-site scripting when rendered. Applications that are single-threaded, use one identical allowlist everywhere, or provide a separate scrubber: are not affected. This issue is fixed in version 1.7.2.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 12:44 UTC
CWE
  • CWE-79 - Improper Neutralization of Input During Web Page Generation
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization
Assigner
GitHub_M CNA under the mitre root
CNA scorecard C 72/100 over 8155 records in the last 180 days details
Impacted products
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-128069",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T12:44:39.599432Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-18T12:45:06.585Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "rails-html-sanitizer",
          "vendor": "rails",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 1.7.2"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Before 1.7.2, the HTML4 and HTML5 variants of Rails::HTML::SafeListSanitizer reuse one Rails::HTML::PermitScrubber across calls and mutate its tags and attributes without synchronization. In a multithreaded process, concurrent sanitize calls using different tags: or attributes: options can interleave and cause one call to use the other call\u0027s allowlist. If a permissive call admits a script element or event-handler attribute, output expected to be sanitized under a stricter policy can retain it and cause cross-site scripting when rendered. Applications that are single-threaded, use one identical allowlist everywhere, or provide a separate scrubber: are not affected. This issue is fixed in version 1.7.2."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 4.7,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "REQUIRED",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-79",
              "description": "CWE-79: Improper Neutralization of Input During Web Page Generation",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T17:17:47.954Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-h7wh-q2qr-458c",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/rails/rails-html-sanitizer/security/advisories/GHSA-h7wh-q2qr-458c"
        },
        {
          "name": "https://github.com/rails/rails-html-sanitizer/issues/228",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails-html-sanitizer/issues/228"
        },
        {
          "name": "https://github.com/rails/rails-html-sanitizer/commit/15f764c3563d5dd9b97ad32eaa7454577ccec4b9",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails-html-sanitizer/commit/15f764c3563d5dd9b97ad32eaa7454577ccec4b9"
        },
        {
          "name": "https://github.com/rails/rails-html-sanitizer/releases/tag/v1.7.2",
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://github.com/rails/rails-html-sanitizer/releases/tag/v1.7.2"
        }
      ],
      "source": {
        "advisory": "GHSA-h7wh-q2qr-458c",
        "discovery": "UNKNOWN"
      },
      "title": "rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-128069",
    "datePublished": "2026-11-13T17:17:47.954Z",
    "dateReserved": "2026-11-12T21:24:51.129Z",
    "dateUpdated": "2026-11-18T12:45:06.585Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-128042 (GCVE-0-2026-128042)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:33 – Updated: 2026-11-13 16:01
VLAI
Title
OpenMage magento-lts before 20.19.0 Race Condition in Coupon Usage Limits
Summary
OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains a race condition in shopping cart price rule usage limits, because Mage_SalesRule_Model_Validator checks coupon limits without locking and the usage counters are later incremented non-atomically. Unauthenticated attackers, including guest shoppers, can submit concurrent checkouts to redeem a limited coupon more times than its cap allows.
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-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
Impacted products
Vendor Product Version
OpenMage magento-lts Affected: 0 , < 20.19.0 (semver)
Unaffected: 20.19.0 (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": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-128042",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T15:29:16.480363Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T16:01:44.930Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "magento-lts",
          "vendor": "OpenMage",
          "versions": [
            {
              "lessThan": "20.19.0",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "20.19.0",
              "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": "reporter",
          "value": "skeletonsec"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "colinmollenhour"
        }
      ],
      "datePublic": "2026-10-26T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "OpenMage magento-lts before 20.19.0 and 21.0.0-beta1 before 21.0.0-beta3 contains a race condition in shopping cart price rule usage limits, because Mage_SalesRule_Model_Validator checks coupon limits without locking and the usage counters are later incremented non-atomically. Unauthenticated attackers, including guest shoppers, can submit concurrent checkouts to redeem a limited coupon more times than its cap allows."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6.3,
            "baseSeverity": "MEDIUM",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "NONE",
            "vulnIntegrityImpact": "LOW"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "HIGH",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 3.7,
            "baseSeverity": "LOW",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:33:56.952Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-5rg7-22cv-c9q6)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/OpenMage/magento-lts/security/advisories/GHSA-5rg7-22cv-c9q6"
        },
        {
          "name": "Patch Commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/OpenMage/magento-lts/commit/2626f027a752cda004c5cf7f8f9bd3cf52f525f2"
        },
        {
          "name": "VulnCheck Advisory: OpenMage magento-lts before 20.19.0 Race Condition in Coupon Usage Limits",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/openmage-magento-lts-before-20.19.0-race-condition-in-coupon-usage-limits"
        }
      ],
      "title": "OpenMage magento-lts before 20.19.0 Race Condition in Coupon Usage Limits",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-128042",
    "datePublished": "2026-11-13T09:33:56.952Z",
    "dateReserved": "2026-11-12T20:45:47.416Z",
    "dateUpdated": "2026-11-13T16:01:44.930Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126287 (GCVE-0-2026-126287)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:36 – Updated: 2026-11-13 21:01
VLAI
Title
NocoDB before 2026.06.2 OAuth Refresh Token Rotation Race Condition
Summary
NocoDB before 2026.06.2 contains a race condition vulnerability in oauth-token.service.ts that allows attackers to reuse a refresh token by presenting it concurrently during non-atomic rotation. Attackers holding a captured refresh token can race the legitimate client to obtain their own access and refresh tokens, retaining scoped access without triggering reuse detection.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 21:01 UTC
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
nocodb nocodb Affected: 0 , < 2026.06.2 (custom)
Unaffected: 2026.06.2 (custom)
    cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-10-27 00:00
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126287",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T21:01:24.325002Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T21:01:35.614Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "nocodb",
          "vendor": "nocodb",
          "versions": [
            {
              "lessThan": "2026.06.2",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "status": "unaffected",
              "version": "2026.06.2",
              "versionType": "custom"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2026.06.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "bytejmp"
        }
      ],
      "datePublic": "2026-10-27T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "NocoDB before 2026.06.2 contains a race condition vulnerability in oauth-token.service.ts that allows attackers to reuse a refresh token by presenting it concurrently during non-atomic rotation. Attackers holding a captured refresh token can race the legitimate client to obtain their own access and refresh tokens, retaining scoped access without triggering reuse detection."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 6,
            "baseSeverity": "MEDIUM",
            "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: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": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.9,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "LOW",
            "privilegesRequired": "LOW",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:36:34.544Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-353r-pj87-54hc)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-353r-pj87-54hc"
        },
        {
          "name": "VulnCheck Advisory: NocoDB before 2026.06.2 OAuth Refresh Token Rotation Race Condition",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/nocodb-before-2026.06.2-oauth-refresh-token-rotation-race-condition"
        }
      ],
      "title": "NocoDB before 2026.06.2 OAuth Refresh Token Rotation Race Condition",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126287",
    "datePublished": "2026-11-13T09:36:34.544Z",
    "dateReserved": "2026-11-10T20:15:03.178Z",
    "dateUpdated": "2026-11-13T21:01:35.614Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126280 (GCVE-0-2026-126280)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:36 – Updated: 2026-11-18 15:47
VLAI
Title
NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation
Summary
NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid authenticated session, and no reuse event is recorded.
SSVC
Exploitation: none Automatable: no Technical Impact: total
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 15:47 UTC
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
nocodb nocodb Affected: 0 , < 2026.08.0 (custom)
Unaffected: 2026.08.0 (custom)
    cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-10-27 00:00
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126280",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T15:47:34.370821Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-18T15:47:46.043Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "nocodb",
          "vendor": "nocodb",
          "versions": [
            {
              "lessThan": "2026.08.0",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "status": "unaffected",
              "version": "2026.08.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2026.08.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "komyunghan"
        }
      ],
      "datePublic": "2026-10-27T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "NocoDB before 2026.08.0 contains a race condition in refresh-token rotation that allows attackers to reuse tokens because UserRefreshToken.ts never checks the affected-row count. Attackers holding a captured refresh token can present it concurrently with the legitimate user to obtain a valid authenticated session, and no reuse event is recorded."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "attackComplexity": "HIGH",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 9.1,
            "baseSeverity": "CRITICAL",
            "privilegesRequired": "NONE",
            "subAvailabilityImpact": "NONE",
            "subConfidentialityImpact": "NONE",
            "subIntegrityImpact": "NONE",
            "userInteraction": "NONE",
            "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/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": 7.4,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "HIGH",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:36:39.321Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-mh65-9xcf-vf8v)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-mh65-9xcf-vf8v"
        },
        {
          "name": "VulnCheck Advisory: NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/nocodb-before-2026.08.0-refresh-token-reuse-via-non-atomic-rotation"
        }
      ],
      "title": "NocoDB before 2026.08.0 Refresh Token Reuse via Non-Atomic Rotation",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126280",
    "datePublished": "2026-11-13T09:36:39.321Z",
    "dateReserved": "2026-11-10T20:14:15.972Z",
    "dateUpdated": "2026-11-18T15:47:46.043Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

CVE-2026-126278 (GCVE-0-2026-126278)

Vulnerability from cvelistv5 – Published: 2026-11-13 09:36 – Updated: 2026-11-13 22:29
VLAI
Title
NocoDB before 2026.08.1 Password Reset Token Race Condition
Summary
NocoDB before 2026.08.1 contains a race condition vulnerability in users.service.ts that allows holders of a valid reset token to perform multiple password changes by sending concurrent reset requests. Attackers can exploit the window created by slow bcrypt hashing before the token is cleared to overwrite the owner's new password and lock them out.
SSVC
Exploitation: none Automatable: yes Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-13 16:34 UTC
CWE
  • CWE-362 - Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Assigner
VulnCheck CNA under the mitre root
CNA scorecard B 84/100 over 8873 records in the last 180 days details
References
Impacted products
Vendor Product Version
nocodb nocodb Affected: 0 , < 2026.08.1 (custom)
Unaffected: 2026.08.1 (custom)
    cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*
Create a notification for this product.
Date Public
2026-10-27 00:00
Credits
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-126278",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-13T16:34:38.890271Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-13T22:29:36.048Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "nocodb",
          "vendor": "nocodb",
          "versions": [
            {
              "lessThan": "2026.08.1",
              "status": "affected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "status": "unaffected",
              "version": "2026.08.1",
              "versionType": "custom"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:nocodb:nocodb:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "2026.08.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "reporter",
          "value": "NinjaGPT"
        }
      ],
      "datePublic": "2026-10-27T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "NocoDB before 2026.08.1 contains a race condition vulnerability in users.service.ts that allows holders of a valid reset token to perform multiple password changes by sending concurrent reset requests. Attackers can exploit the window created by slow bcrypt hashing before the token is cleared to overwrite the owner\u0027s new password and lock them out."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "NONE",
            "attackVector": "NETWORK",
            "baseScore": 8.7,
            "baseSeverity": "HIGH",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "NONE",
            "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:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS"
        },
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "NONE",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
            "version": "3.1"
          },
          "format": "CVSS"
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-362",
              "description": "Concurrent Execution using Shared Resource with Improper Synchronization (\u0027Race Condition\u0027)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-13T09:36:41.678Z",
        "orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
        "shortName": "VulnCheck"
      },
      "references": [
        {
          "name": "GitHub Security Advisory (GHSA-7mf9-q77p-r4r3)",
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://github.com/nocodb/nocodb/security/advisories/GHSA-7mf9-q77p-r4r3"
        },
        {
          "name": "VulnCheck Advisory: NocoDB before 2026.08.1 Password Reset Token Race Condition",
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://www.vulncheck.com/advisories/nocodb-before-2026.08.1-password-reset-token-race-condition"
        }
      ],
      "title": "NocoDB before 2026.08.1 Password Reset Token Race Condition",
      "x_generator": {
        "engine": "vulncheck-endgame"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
    "assignerShortName": "VulnCheck",
    "cveId": "CVE-2026-126278",
    "datePublished": "2026-11-13T09:36:41.678Z",
    "dateReserved": "2026-11-10T20:14:15.972Z",
    "dateUpdated": "2026-11-13T22:29:36.048Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Mitigation
Architecture and Design

In languages that support it, use synchronization primitives. Only wrap these around critical code to minimize the impact on performance.

Mitigation
Architecture and Design

Use thread-safe capabilities such as the data access abstraction in Spring.

Mitigation
Architecture and Design
  • Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
  • Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).
Mitigation
Implementation

When using multithreading and operating on shared variables, only use thread-safe functions.

Mitigation
Implementation

Use atomic operations on shared variables. Be wary of innocent-looking constructs such as "x++". This may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read, followed by a computation, followed by a write.

Mitigation
Implementation

Use a mutex if available, but be sure to avoid related weaknesses such as CWE-412.

Mitigation
Implementation

Avoid double-checked locking (CWE-609) and other implementation errors that arise when trying to avoid the overhead of synchronization.

Mitigation
Implementation

Disable interrupts or signals over critical parts of the code, but also make sure that the code does not go into a large or infinite loop.

Mitigation
Implementation

Use the volatile type modifier for critical variables to avoid unexpected compiler optimization or reordering. This does not necessarily solve the synchronization problem, but it can help.

Mitigation MIT-17
Architecture and Design Operation

Strategy: Environment Hardening

Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

CAPEC-26: Leveraging Race Conditions

The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.

CAPEC-29: Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions

This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.