pydantic-deep is vulnerable to Protection Mechanism Failure
51
Medium Risk
The browser allowlist was only enforced on direct navigate() calls, leaving other navigation paths such as link clicks, JavaScript redirects, and history navigation outside the restriction boundary. As a result, a model or attacker controlling browser actions could still reach disallowed domains and interact with unintended external content despite an allowed_domains policy being configured. An attacker might exploit this by placing a cross-domain link on an allowed page, triggering execute_js to set location.href to an attacker-controlled site, or using go_back / go_forward to load previously visited disallowed pages, potentially exposing the model to malicious content, data exfiltration workflows, or policy bypass. The fix adds defense-in-depth by blocking top-level disallowed navigations at the network layer and validating the final page URL after each navigation-capable action.
You are affected if you are using a version that falls within the vulnerable range and rely on allowed_domains for the browser capability, any user/model-driven navigation via click, execute_js, history, or popups could bypass the boundary.
pydantic-deep is vulnerable to Protection Mechanism Failure in versions 0.1.0 - 0.3.22.
Upgrade the pydantic-deep library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

SOC 2Compliant
ISO 27001Compliant