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.
CVE-2026-58203
This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EPSS
- 2.6%
- KEV
- Not listed
Published
July 6, 2026
Last Modified
July 9, 2026
Advisory Details (1)
Auto-updated Jul 8, 2026NestedSecretsSettingsSource follows symlinks outside secrets_dir, enabling local file read and bypassing secrets_dir_max_size · Advisory · pydantic/pydantic-settings · GitHub
https://github.com/pydantic/pydantic-settings/security/advisories/GHSA-4xgf-cpjx-pc3jAffected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pydantic-settings | 2.12.0, 2.13.0, 2.13.1, 2.14.0, 2.14.1 | 2.14.2 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-10 23:19 UTCEG score recompute
- 2026-07-09 21:26 UTCEG score recompute
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 19:34 UTCEG score recompute
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 17:40 UTCEG score recompute
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 15:37 UTCEG score recompute
- 2026-07-06 15:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-22 · CWE-59 · CWE-400
Frequently asked(5)
What is CVE-2026-58203?
When was CVE-2026-58203 disclosed?
Is CVE-2026-58203 actively exploited?
What is the CVSS score of CVE-2026-58203?
How do I remediate CVE-2026-58203?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-58203
Is Your Infrastructure Affected by CVE-2026-58203?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.