VulnerabilityPublished 4 Aug 2026

CVE-2026-18817: Baserow · Improper Authorization

Affects BaserowSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.1 Low · fixed in 2.3.3 : update Baserow when convenient.

Data as of 3 Nov 2026, 22:58 UTC

CVSS 4.0 base score

2.1Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.3.3

CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Baserow	Affected =2.3.0 =2.3.1 =2.3.2	Fixed in–
PyPIbaserow`pkg:pypi/baserow`Other threats	Affected =2.3.0 =2.3.1 =2.3.2	Fixed in–

CPE configurations (1)

cpe:2.3:a:baserow:baserow:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Baserow to version 2.3.3 or later to resolve this issue. Since the maintainer considers this more of a bug than a vulnerability and no endpoints are accessible with the affected tokens, no additional mitigation steps are explicitly required.

Description

CVE-2026-18817 is a low-severity security issue in Baserow versions 2.3.0 through 2.3.2 involving improper authorization in the BaserowImpersonateAuthTokenSerializer function. The flaw allows token generation for inactive non-staff users, but the project maintainer notes that no endpoints actually work with these tokens, suggesting it is more a bug than a vulnerability. Remote exploitation is possible but considered difficult and of high complexity. Upgrading to version 2.3.3 resolves the issue.

Impact

The impact is limited due to the fact that tokens issued for inactive users do not allow access to any endpoints, reducing the risk of unauthorized actions. The CVSS score is low (2.1), reflecting the low severity and difficulty of exploitation. No known exploits are reported in the wild.

Summary

This vulnerability affects Baserow versions 2.3.0, 2.3.1, and 2.3.2 in the Inactive Non-Staff User Handler component, specifically the BaserowImpersonateAuthTokenSerializer function. Improper authorization occurs due to token issuance for deactivated users, but these tokens do not grant access to any endpoints. The maintainer indicates uncertainty about the vulnerability status, describing it as likely a bug. Remote exploitation is possible but complex and difficult. The issue is fixed in version 2.3.3.

References

Community reviews

Loading reviews…