This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Search vulnerabilities
jsbroks COCO Annotator Data Endpoint datasets.py path traversal
A weakness has been identified in jsbroks COCO Annotator up to 0.11.1. Affected is an unknown function of the file backend/webserver/api/datasets.py of the component Data Endpoint. Executing a manipulation of the argument folder can lead to path traversal. The attack can be launched remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
LiteLLM: MCP Authentication Bypass via OAuth2 Passthrough Fallback
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.84.0, LiteLLM's MCP Streamable HTTP endpoint allowed an unauthenticated attacker to use a fabricated Authorization header to trigger an OAuth2 passthrough fallback path that replaced failed LiteLLM key validation with an empty UserAPIKeyAuth() object, allowing requests to reach MCP tooling without a valid LiteLLM key. This issue is fixed in version 1.84.0.
Low-privilege users may remove protected Artifactory metadata
A low-privilege authenticated user may permanently remove protected internal metadata across repositories under specific conditions.
Deleted users may temporarily retain access to JFrog Artifactory
Credentials for a deleted user may remain valid for a short period under specific conditions.
Anonymous users may access restricted Artifactory repository information
An unauthenticated user may access restricted repository information under specific conditions.
Authenticated users may access private NuGet metadata
An authenticated user without repository read permission may access private NuGet metadata under specific conditions.
Authenticated users may access private OCI referrer metadata
An authenticated user without repository read permission may access private OCI referrer metadata under specific conditions.
Repository readers may access content outside configured upstream paths
A repository reader with cache-deploy permission may access content outside a configured upstream path under specific conditions.
Authenticated users may write files outside the intended Artifactory work directory
An authenticated user may write files outside the intended Artifactory work directory under specific conditions.
Project Resource Managers may escalate privileges in JFrog Artifactory
A Project Resource Manager may gain broader administrative privileges under specific conditions.
Anonymous users may access restricted Artifactory content under specific configurations
An unauthenticated user may access restricted Artifactory content when a credentialed remote repository is configured in a specific way.
Publishers without delete permission can overwrite docker layer information
A repository publisher without delete permission may modify protected package content under specific conditions.
Bundle writers may alter trusted release information in JFrog Artifactory
A bundle writer may create misleading release promotion information under specific conditions.
Potential insecure deserialization in JFrog Artifactory
A party with write access to stored session data may affect JFrog Artifactory under specific conditions.
Potential improper SAML signature verification in JFrog Artifactory
A user with access to a valid SAML response may impersonate another user under specific conditions.
Potential remember-me authentication bypass in JFrog Artifactory
An unauthenticated user may bypass authentication under specific cache conditions.
Authenticated users may access restricted Artifactory support information
A low-privileged authenticated user may access restricted support information under specific conditions.
Integration credential holders may impersonate users in JFrog Access
A holder of a valid integration credential may impersonate other users under specific conditions.
GitPython before 3.1.58 Config Injection via option-name
GitPython before 3.1.58 contains a config-name injection vulnerability in the option-name validator that allows attackers to forge arbitrary git-config directives by injecting equals signs, hash symbols, and whitespace into option names. Attackers can inject malicious option names like 'sshCommand = touch /tmp/RCE #' to execute arbitrary commands via core.sshCommand or core.hooksPath on the next git operation.