Venueless privilege escalation via leaked room permissions
- Exploited
- No known exploitation
- Fix
- Fixed in 12a4a2e3
- Who is exposed
- Not reported
Summary
Venueless, from pretix, has a flaw where room permissions leak into a user's world permissions during certain actions. An attacker who can reach it over the network and has a low-privilege account could gain permissions beyond what they should have.
Written by a model
Original description
A bug caused room permissions to leak into the world permissions of the acting user during certain actions.
What to do
Upgrade to a fixed version: 12a4a2e3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131171 (Room and world premissions not clearly separated), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131171 (entry last updated 2026-11-20):
Affected:
- pretix Venueless: fixed in 12a4a2e3
Fixed versions: 12a4a2e3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131171 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131171 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/venueless/venueless/security/advisories/GHSA-957c-gqp9-88hr
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131171
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131171"}.Affected versions
- venfixed in 12a4a2e3
cve.now Index
- Exploitation0/40No signal
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · venueless/venueless · Advisory GHSA-957c-gqp9-88hr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131171 |
| Record | NVD · CVE-2026-131171 |
Questions about CVE-2026-131171
Is CVE-2026-131171 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131171?
ven: before 12a4a2e3.
Source: cve.now feed data
How do I fix CVE-2026-131171?
Upgrade to a fixed version: 12a4a2e3.
Source: cve.now feed data
Related
- CVE-2026-130608When using the admin area profile form to change ones profile details except the password (so, email or username), the password field in…
- CVE-2026-5599API allows deletion of users of other instance
- CVE-2026-4982Unauthorized access to chat contents
- CVE-2026-82838Default webserver configuration with incorrect CSP
- CVE-2026-12863Open redirect
- CVE-2026-12862XLSX formula injection in exports
No corrections so far. Something wrong on this page? Report an error.