CVE-2026-40077 Vulnerability Analysis & Exploit Details

CVE-2026-40077
Vulnerability Scoring

3.5
/10
Moderate Risk

Exploiting CVE-2026-40077 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-40077 Details

Status: Analyzed

Last updated: 🕘 26 Oct 2026, 21:10 UTC
Originally published on: 🕗 09 Apr 2026, 20:16 UTC

Time between publication and last update: 200 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N

CVE-2026-40077 Vulnerability Summary

CVE-2026-40077: 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.

Assessing the Risk of CVE-2026-40077

Access Complexity Graph

The exploitability of CVE-2026-40077 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-40077

This vulnerability, CVE-2026-40077, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-40077, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-40077, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-40077 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-40077 poses no threat to data integrity.
  • Availability: None
    CVE-2026-40077 does not impact system availability.

CVE-2026-40077 References

External References

CWE Common Weakness Enumeration

CWE-184

CAPEC Common Attack Pattern Enumeration and Classification

  • Double Encoding CAPEC-120 The adversary utilizes a repeating of the encoding process for a set of characters (that is, character encoding a character encoding of a character) to obfuscate the payload of a particular request. This may allow the adversary to bypass filters that attempt to detect illegal characters or strings, such as those that might be used in traversal or injection attacks. Filters may be able to catch illegal encoded strings, but may not catch doubly encoded strings. For example, a dot (.), often used in path traversal attacks and therefore often blocked by filters, could be URL encoded as %2E. However, many filters recognize this encoding and would still block the request. In a double encoding, the % in the above URL encoding would be encoded again as %25, resulting in %252E which some filters might not catch, but which could still be interpreted as a dot (.) by interpreters on the target.
  • Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • Flash Injection CAPEC-182 An attacker tricks a victim to execute malicious flash content that executes commands or makes flash calls specified by the attacker. One example of this attack is cross-site flashing, an attacker controlled parameter to a reference call loads from content specified by the attacker.
  • Using Leading 'Ghost' Character Sequences to Bypass Input Filters CAPEC-3 Some APIs will strip certain leading characters from a string of parameters. An adversary can intentionally introduce leading "ghost" characters (extra characters that don't affect the validity of the request at the API layer) that enable the input to pass the filters and therefore process the adversary's input. This occurs when the targeted API will accept input data in several syntactic forms and interpret it in the equivalent semantic way, while the filter does not take into account the full spectrum of the syntactic forms acceptable to the targeted API.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Argument Injection CAPEC-6 An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
  • Using Unicode Encoding to Bypass Validation Logic CAPEC-71 An attacker may provide a Unicode string to a system component that is not Unicode aware and use that to circumvent the filter or cause the classifying mechanism to fail to properly understanding the request. That may allow the attacker to slip malicious data past the content filter and/or possibly cause the application to route the request incorrectly.
  • User-Controlled Filename CAPEC-73 An attack of this type involves an adversary inserting malicious characters (such as a XSS redirection) into a filename, directly or indirectly that is then used by the target software to generate HTML text or other potentially executable content. Many websites rely on user-generated content and dynamically build resources like files, filenames, and URL links directly from user supplied data. In this attack pattern, the attacker uploads code that can execute in the client browser and/or redirect the client browser to a site that the attacker owns. All XSS attack payload variants can be used to pass and exploit these vulnerabilities.
  • AJAX Footprinting CAPEC-85 This attack utilizes the frequent client-server roundtrips in Ajax conversation to scan a system. While Ajax does not open up new vulnerabilities per se, it does optimize them from an attacker point of view. A common first step for an attacker is to footprint the target environment to understand what attacks will work. Since footprinting relies on enumeration, the conversational pattern of rapid, multiple requests and responses that are typical in Ajax applications enable an attacker to look for many vulnerabilities, well-known ports, network locations and so on. The knowledge gained through Ajax fingerprinting can be used to support other attacks, such as XSS.

Vulnerable Configurations

  • cpe:2.3:a:beszel:beszel:0.0.1:-:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:-:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha0:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha0:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha1:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha1:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha2:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha2:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha3:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha3:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha4:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha4:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha5:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha5:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha6:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha6:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha7:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha7:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha8:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha8:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.0.1:alpha9:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.0.1:alpha9:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.1.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.1.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.10.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.11.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.11.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.0:-:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.0:-:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.3:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.3:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.4:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.4:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.5:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.5:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.6:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.6:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.7:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.7:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.8:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.8:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.9:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.9:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.10:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.10:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.11:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.11:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.12.12:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.12.12:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.13.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.13.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.13.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.13.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.14.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.14.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.15.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.15.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.15.3:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.15.3:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.15.4:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.15.4:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.16.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.16.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.17.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.0:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.0:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.1:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.1:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.2:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.2:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.3:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.3:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.4:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.4:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.5:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.5:*:*:*:*:*:*:*
  • cpe:2.3:a:beszel:beszel:0.18.6:*:*:*:*:*:*:*
    cpe:2.3:a:beszel:beszel:0.18.6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-40077: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-118129 – A vulnerability was found in jeremyckahn Chitchatter up to f82538633813c854a81a8b2112a2f6ba17b39cbc. The affected element is the function isConfigM...
  • CVE-2026-104895 – The asynchronous Smile parser (NonBlockingByteArrayParser) uses a raw-binary length prefix taken from untrusted input to allocate a byte[] before t...
  • CVE-2026-104016 – ProtobufParser parses length-prefixed protobuf string and bytes fields by checking (_inputPtr + len) <= _inputEnd and then, on the fast path, calli...
  • CVE-2026-59158 – Nuxt Ollama integrates the official Ollama JavaScript library into Nuxt applications. Prior to 1.3.1, `src/module.ts` unconditionally merges all mo...
  • CVE-2026-58496 – Thor Vector Graphics (ThorVG) is a production-ready vector graphics engine. Prior to 1.0.7, the `SFNT/TTF` font loader's `SfntLoader::gen` function...