NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
CRITICAL severity

CVE-2018-1002150 — koji

CRITICAL

CVE-2018-1002150 is a critical-severity (CVSS 9.1) CWE-732 vulnerability in koji. A fix is available for koji — see the affected versions and patch details below.

Koji hub call does not perform correct access checks

Also known asPYSEC-2018-86
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk
0.00%0.74%1.48%2.22%0.3%1.7%May 26Sep 26Nov 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐍koji🐍koji🐍koji🐍koji

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

Koji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access. This vulnerability has been fixed in versions 1.12.1, 1.13.1, 1.14.1 and 1.15.1.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIkoji≥ 1.15&&< 1.15.11.15.1pip install --upgrade 'koji==1.15.1'
🐍PyPIkoji≥ 1.14&&< 1.14.11.14.1pip install --upgrade 'koji==1.14.1'
🐍PyPIkoji≥ 1.13&&< 1.13.11.13.1pip install --upgrade 'koji==1.13.1'
🐍PyPIkoji≥ 1.12&&< 1.12.11.12.1pip install --upgrade 'koji==1.12.1'

Affected Products

1 product · 4 configurations
Application
kojikoji_project
4 versions
1.12.01.13.01.14.01.15.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update koji to 1.15.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1002150 is resolved across your whole dependency graph.

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Koji version 1.12, 1.13, 1.14 and 1.15 contain an incorrect access control vulnerability resulting in arbitrary filesystem read/write access. This vulnerability has been fixed in versions 1.12.1, 1.13.1, 1.14.1 and 1.15.1.
O3 Security · Impact-Aware SCA

Is CVE-2018-1002150 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-1002150: koji — Fixed in 1.15.1