Understand vulnerabilities. Protect your applications.
Discover which vulnerabilities affect your technologies and how to fix them. Explore clear explanations, affected versions and practical recommendations - from CMS platforms and plugins to application libraries.
Vulnerability archive 4,358
Reset filtersAn issue was discovered in Django 5.2 before 5.2.15 and 6.0 before 6.0.6.
Django fails to prevent reuse of a partially-initialized connection after a failed `STARTTLS` handshake
Django: signed cookies are vulnerable to salt namespace collisions
huggingface/transformers: Arbitrary Code Execution During Model Initialization in the LightGlue Model Loading Path
Django: has_vary_header may expose cached responses when Vary values contain whitespace
A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables in AI Gateway secrets, which can be exploited to exfiltrate sensitive server-side environme
OpenCTI is an open source platform for managing cyber threat intelligence knowledge and observables. Versions prior to 7.260227.0 are vulnerable to XSS in the rendering of email-message observable bod
AIOHTTP is vulnerable to cross-origin redirect with per-request cookies
AIOHTTP is Vulnerable to Deserialization of Untrusted Data
MLflow: Any authenticated user can enumerate all gateway secrets, endpoints, and model definitions
praisonai-platform: Any workspace member can add arbitrary user as owner via POST /workspaces/{id}/members
Apache Airflow has no certificate validation on SMTP STARTTLS connections
Apache Airflow: Execution API JWT leaked via KubernetesExecutor worker command-line args
Apache Airflow has an Authorization Bypass Through User-Controlled Key
A bug in Apache Airflow's auth manager logout handling left previously-issued JWT tokens valid after the user clicked logout in the UI: the logout flow for `FabAuthManager` and `KeycloakAuthManager` d
Apache Airflow Vulnerable to Exposure of Sensitive Information to an Unauthorized Actor
Exploitation requires the attacker to already be an authenticated Airflow worker holding a valid Log-server JWT issued for at least one Dag. Apache Airflow's Log server authorized JWT tokens against D
A bug in Apache Airflow's XCom PATCH endpoint `PATCH /api/v2/xcomEntries/{key}` allowed an authenticated UI/API user with XCom write permission on a Dag to set XCom entries under reserved key names (e
A bug in Apache Airflow's rendered-template field handling caused nested sensitive-key masking (e.g. nested `password` / `token` / `secret` / `api_key` keys inside a JSON template structure) to be byp
A bug in Apache Airflow's bulk Task Instances API (`PATCH/DELETE /api/v2/dags/{dag_id}/dagRuns/{dag_run_id}/taskInstances`) evaluated authorization against the `dag_id` resolved from the URL path whil
Apache Airflow's official documentation at `core-concepts/dag-run.html` ("Passing Parameters when triggering Dags") showed a verbatim `BashOperator(bash_command="echo value: {{ dag_run.conf['conf1'] }
Apache Airflow has an Improper Authorization issue
Apache Airflow: Authenticated users can bypass the `is_safe_url` check
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.