Faze-Up

**Name of the Vulnerable Software and Affected Versions** SeaweedFS versions prior to 4.40 **Description** The S3 API accepts an external OIDC JWT (OpenID Connect JSON Web Token) sent directly in the `Authorization` header and maps it to an IAM role without enforcing the trust policy of that role. While the standard STS `AssumeRoleWithWebIdentity()` path correctly rejects tokens when the trust policy does not trust the federated provider, the direct S3 bearer path only validates the token itself. This allows a valid OIDC user to bypass trust policy restrictions and obtain S3 access, including the ability to read, write, and delete objects, by presenting the raw OIDC JWT directly to the S3 API. **Recommendations** Update to version 4.40.

**Name of the Vulnerable Software and Affected Versions** GitPython version 3.1.50 **Description** An issue exists where the software fails to recognize joined short-option forms, such as `-u<value>`, which is the short form of `--upload-pack=<value>`, when enforcing its default unsafe-option gate. If an application passes attacker-influenced clone options into the `Repo.clone from()` function using the `multi options` parameter while `allow unsafe options` is set to `False`, an attacker can provide `-u<helper>` to bypass the security gate. This allows the execution of an arbitrary helper command during the clone process. **Recommendations** Update GitPython to version 3.1.51.

**Name of the Vulnerable Software and Affected Versions** protobufjs versions 8.2.0 through 8.6.4 **Description** The protobufjs Text Format extension parses string-keyed map entries using ordinary property assignment. This allows a map entry with the key ` proto ` to modify the prototype of the returned map object instead of creating a standard map entry in protobufjs/ext/textformat. Prototype pollution occurs when an attacker can manipulate the ` proto ` property, potentially leading to unexpected behavior or security bypasses by altering the base object properties inherited by other objects. **Recommendations** Update to version 8.6.5.

**Name of the Vulnerable Software and Affected Versions** pydantic-settings versions 2.12.0 through 2.14.1 **Description** The `NestedSecretsSettingsSource` reads secret values from files within a configured `secrets dir`. When the `secrets nested subdir` variable is set to true, the system follows symbolic links within the `secrets dir` that point to locations outside that directory, allowing files from external paths to be read into settings values. This process also bypasses the `secrets dir max size` protection, which is intended to cap the loading size. An attacker or a lower-privileged component with the ability to modify entries in the configured secrets directory, such as through a writable or shared secrets mount, can exploit this to perform an unintended local file read and circumvent the size limit. **Recommendations** Update pydantic-settings to version 2.14.2.