pydantic up to 2.14.1 Secrets Settings Source information disclosure

Summaryinfo

A vulnerability, which was classified as problematic, was found in pydantic up to 2.14.1. Affected by this issue is some unknown functionality of the component Secrets Settings Source. The manipulation results in information disclosure. This vulnerability is identified as CVE-2026-58203. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in pydantic up to 2.14.1. It has been classified as problematic. Affected is some unknown functionality of the component Secrets Settings Source. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-58203 since 06/29/2026. The exploitability is told to be easy. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 2.14.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-41878). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• pydantic

Version

• 2.14.0
• 2.14.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion