How severe is CVE-2025-14881?

No CVSS score has been assigned to CVE-2025-14881 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-14881?

CVE-2025-14881 affects the following packages: pretix (PyPI), pretix (PyPI), pretix (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2025-14881?

Update pretix to 2025.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14881 is resolved across your whole dependency graph.

How do I detect CVE-2025-14881 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pretix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-14881 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2025-14881 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-14881 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-14881?

CVE-2025-14881 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-14881?

CVE-2025-14881 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-14881 published, and has it been updated?

CVE-2025-14881 was published on December 19, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2025-14881 — pretix

Fix: pretix/pretix@4b56518

CVE-2025-14881 is a CWE-639 vulnerability in pretix. A fix is available for pretix — see the affected versions and patch details below.

Insecure direct object reference

Also known asGHSA-r2h2-g46h-8mx8PYSEC-2026-1803

Published

Dec 19, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-14881.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

🐍pretix🐍pretix🐍pretix

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Multiple API endpoints allowed access to sensitive files from other users by knowing the UUID of the file that were not intended to be accessible by UUID only.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pretix`	≥ 2025.10.0&&< 2025.10.1	2025.10.1`pip install --upgrade 'pretix==2025.10.1'`
🐍PyPI	`pretix`	≥ 2025.9.0&&< 2025.9.3	2025.9.3`pip install --upgrade 'pretix==2025.9.3'`
🐍PyPI	`pretix`	all versions	2025.8.3`pip install --upgrade 'pretix==2025.8.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pretix, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pretix to 2025.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-14881 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Multiple API endpoints allowed access to sensitive files from other users by knowing the UUID of the file that were not intended to be accessible by UUID only.

O3 Security · Impact-Aware SCA

Is CVE-2025-14881 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works