CVE-2026-26720
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue in Twenty CRM v1.15.0 and before allows a remote attacker to execute arbitrary code via the local.driver.ts module.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA Remote Code Execution (RCE) vulnerability exists in the local.driver.ts module of Twenty CRM v1.15.0 and prior versions. The CVSS 9.8 score indicates the flaw is exploitable over the network without authentication or user interaction, allowing attackers to execute arbitrary code on the affected system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.15.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Twenty CRM installation versionQuery your Twenty CRM instance for its version number. This is typically available via the admin dashboard, API endpoint (such as /api/version or /api/health), or by inspecting the package.json file in the installation directory if you have filesystem access.Affected if The displayed version is 1.15.0 or any version prior to 1.15.0
-
Locate the local.driver.ts moduleSearch the Twenty CRM source code or installation directory for a file named local.driver.ts. This file is part of the CRM codebase and handles local driver functionality.Affected if The local.driver.ts file exists in your installation and you are running an affected version (1.15.0 or prior)
-
Verify module is actively loadedExamine your Twenty CRM configuration, module registry, or runtime environment to determine whether the local.driver.ts module is being imported and executed at runtime.Affected if The local.driver module is loaded and running on an affected version (1.15.0 or prior)
-
Assess network accessibilityDetermine if your Twenty CRM instance is exposed to network access. Check firewall rules, reverse proxy configuration, and bind addresses to see if the application is reachable over the network.Affected if The CRM is network-accessible (not localhost-only or firewalled) while running an affected version with the local.driver module enabled
Your environment is affected if you are running Twenty CRM version 1.15.0 or earlier AND the local.driver.ts module is present and active in your installation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImmediately update to a patched version of Twenty CRM once available. As an interim measure, restrict network access to the CRM application and review the local.driver.ts module for insecure input handling or improper path traversal issues.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26720 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-26720 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data