Path Traversal in Pydantic (CVE-2026-58203)
Summary
Path traversal in Pydantic (CVE-2026-58203). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.14.2 or later.
Original description
The description as published by the source.
pydantic-settings provides settings management using Pydantic. From 2.12.0 until 2.14.2, NestedSecretsSettingsSource reads secret values from files in a configured secrets_dir. When secrets_nested_subdir=True, a directory entry inside secrets_dir that is a symbolic link pointing outside secrets_dir is followed, so files outside the configured directory are read into settings values. The same code path bypasses the documented secrets_dir_max_size protection. An attacker or lower-privileged component able to influence entries in the configured secrets directory (for example, a writable or shared secrets mount) can turn this into an unintended local file read into settings and can defeat the advertised loading-size cap. This vulnerability is fixed in 2.14.2.
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-58203 has been found in Pydantic.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade Pydantic to 2.14.2 or later.
If unsure, ask your IT team or search "Pydantic CVE-2026-58203" on the vendor's site.
CVE-2026-58203 (Pydantic) — CWE-22 / CVSS v3 5.3
Attack vector: local / no user interaction
Patched: 2.14.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.
Path traversal (CWE-22) exists in Pydantic.
Check the vendor advisory for the affected versions of Pydantic.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.14.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Pydantic' . 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
-
1Identify exposure identify
grep -r 'Pydantic' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Pydanticを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Pydantic to 2.14.2ステージング環境で 2.14.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-58203 pydantic-settings Fixed in: 2.14.2-1
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov