Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 04:05 UTC

Critical in the last 24 hours

1602 in 30 days

Newly known exploited

In the last 24 hours, CISA KEV and vendor reports

Sources checked

Every hour, see the list

New in the last 24 hours

156-74% vs 7-day avg of 598

2 critical, 44 high, 62 medium, 28 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Medium	6.5	CVE-2026-115886	MLflow is an open source AI engineering platform for agents, large language models, and machine learning models mlflowmlflow	NVD	Oct 23 22:16 UTC
CVE-2026-115886MLflow is an open source AI engineering platform for agents, large language models, and machine learning models Executive summary The advisory is a code diff for MLflow, an open source AI engineering platform, that adds server-side checks on serialized scorer payloads. It describes the change as closing a gap where scorer data the server could execute or use to steer outbound requests was not validated when sent directly to the REST API. The advisory does not state a severity rating, and it does not state a specific vendor recommendation beyond the code change itself. Technical summary The diff adds a helper, _validate_serialized_scorer_payload, that rejects decorator scorers carrying a call_source field, since that field is executed via exec() during deserialization, and applies this check to request payloads and to scorers fetched from the store. It also adds _validate_third_party_scorer_data, which rejects non-object kwargs and gateway destination keys such as api_base at any nesting depth, because these could direct the judge's LLM client to an attacker-chosen host. The advisory does not state the vulnerability class by name, the CVSS score, the attack preconditions beyond direct REST API access, affected version ranges, fixed version numbers, workarounds, or exploitation status, and these are not stated. No detection guidance is given. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/mlflow/mlflow/commit/bac30b4…d4db07ae60ab3838803f Impact if exploited ConfidentialityLow IntegrityLow AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Privileges required None User interaction None Scope Unchanged CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N Affects mlflow mlflow NIST National Vulnerability DatabasePublished Oct 23, 2026 22:16 UTC Read the advisory
	High	8.8	CVE-2026-53995	MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by... mlflowmlflow	NVD	Oct 19 22:17 UTC
CVE-2026-53995MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by... From the advisory MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions. FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected. Impact if exploited ConfidentialityNone IntegrityHigh AvailabilityLow How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required None User interaction None CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Affects mlflow mlflow NIST National Vulnerability DatabasePublished Oct 19, 2026 22:17 UTC Read the advisory

Example	Finds
	Every word appears somewhere: title, summaries, IDs, vendor, or product
	An exact phrase
	One vendor. product: for a product, vp: for either
	Commas mean any of them, in every field
	Severity: critical, high, medium, low, or unknown
	CVSS score, with >, >=, <, or <=
	A score range
	Known exploited. is:kev works too, and kev:no leaves them out
	One source, by name
	Confidentiality impact: high, low, none, or any (low or high)
	Integrity and availability work the same way
	An advisory or CVE ID, or part of one
	A minus sign leaves out whatever the term matches

Vulnerability feed

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee