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

154-74% vs 7-day avg of 597

2 critical, 44 high, 61 medium, 27 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	High	7.4	CVE-2026-110975	A flaw was found in Kruize Autotune KruizeKruize Autotune	NVD		Oct 23 18:17 UTC
CVE-2026-110975A flaw was found in Kruize Autotune Executive summary Kruize Autotune exposed the stored login secrets for its monitoring data sources, including passwords, tokens, API keys, and OAuth2 client secrets, to any client that can reach the service. Anyone who could reach the service could take these credentials and reuse them against the backing monitoring systems. The advisory says the fix is in Autotune 0.11.2, which removes the secrets from the affected responses and tightens the CORS policy. Technical summary The flaw is an information exposure caused by serializing datasource objects with default Gson settings and no field exclusion, classified as CWE-256 (Plaintext Storage of a Password) in the advisory's references. The REST API has no authentication layer, so any client with network access to the service can call GET /datasources or the datasource-metadata endpoint and read cleartext credentials. The advisory states that the NodePort, LoadBalancer, and OpenShift Route configurations make the service remotely reachable. The issue is fixed in Autotune 0.11.2 by a Gson exclusion strategy on AuthenticationConfig and a deny-by-default CORS handler. The advisory states that credentials stored in cleartext at rest in the kruize_authentication table are not addressed by this fix. Workarounds and detection guidance are not stated in the advisory. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from access.redhat.com/security/cve/CVE-2026-110975 Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone How it is exploited Attack vector Adjacent network Attack complexity Low Privileges required None User interaction None Scope Changed CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N Affects Kruize Kruize Autotune NIST National Vulnerability DatabasePublished Oct 23, 2026 18: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

Search syntax

Welcome to CVEsee.org

What is CVEsee.org?

Disclaimer

You are leaving CVEsee.org

Install CVEsee