Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-15529 medium CVSS 6.3

Vulnerability in pyod (CVE-2026-15529)

Summary

Vulnerability in pyod (CVE-2026-15529). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.6.2 or later.

Original description

The description as published by the source.

A vulnerability was detected in yzhao062 pyod 3.5.0/3.5.1/3.5.2. Affected is the function pyod.utils.persistence.load of the file pyod/utils/persistence.py. Performing a manipulation of the argument path results in deserialization. The attack can be initiated remotely. The pull request to fix this issue requires some minor changes.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-15529 has been found in pyod.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade pyod to 3.6.2 or later.
If unsure, ask your IT team or search "pyod CVE-2026-15529" on the vendor's site.

CVE-2026-15529 (pyod) — CWE-20 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.6.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-20) exists in pyod.

📍 Affected scope

Check the vendor advisory for the affected versions of pyod.

🔥 Severity

Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.6.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pyod' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'pyod' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pyod を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade pyod to 3.6.2

    ステージング環境で 3.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip pyod
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details