Skip to main content
VulnerabilityPublished Updated

CVE-2026-40077: henrygd beszel · Incomplete List of Disallowed Inputs

Affects henrygd beszelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.5 Low : upgrade to 0.18.7 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
3.5Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.18.7
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 30 Oct 2026.

What to do

Upgrade beszel and henrygd/beszel to 0.18.7.

Affected software

ProductAffectedFixed in
henrygdbeszelAffected
  • <0.18.7
Fixed in
  • 0.18.7
GitHubhenrygd/beszelpkg:github/henrygd/beszelOther threatsAffected
  • <0.18.7
Fixed in
  • 0.18.7

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

AI-suggested

Upgrade beszel to version 0.18.7 or later where this vulnerability is fixed. Since the vendor advisory confirms the issue is resolved in 0.18.7, applying this official fix fully mitigates the risk. No additional mitigation steps are indicated.

Description

Beszel is a server monitoring platform. Prior to 0.18.7, some API endpoints in the Beszel hub accept a user-supplied system ID and proceed without further checks that the user should have access to that system. As a result, any authenticated user can access these routes for any system if they know the system's ID. System IDs are random 15 character alphanumeric strings, and are not exposed to all users. However, it is theoretically possible for an authenticated user to enumerate a valid system ID via web API. To use the containers endpoints, the user would also need to enumerate a container ID, which is 12 digit hexadecimal string. This vulnerability is fixed in 0.18.7.

References

Community reviews

Loading reviews…