Vulnerability feed

CVE and vendor PSIRT advisories from 13 sources, last 30 days. Updated hourly, last run Oct 26 07: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

164-72% vs 7-day avg of 596

3 critical, 57 high, 70 medium, 29 low

Expand	Severity	Score	Advisory	Title	Source	Flags	Published
	Medium	4.8	CVE-2026-115749	hydra-ray-launcher 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2 contains an arbitrary module import vulnerability via the ray_pkg_version OmegaConf resolver passing... hydra-ecosystem, hydra-ray-launcherhydra-ecosystem hydra-ray-launcher, hydra-ray-launcher	NVD		Oct 23 13:17 UTC
CVE-2026-115749hydra-ray-launcher 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2 contains an arbitrary module import vulnerability via the ray_pkg_version OmegaConf resolver passing... Executive summary The advisory says hydra-ray-launcher versions 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2 contain an arbitrary module import flaw, reachable through the ray_pkg_version OmegaConf resolver. The advisory does not state a severity rating, and the vendor's recommended fix is to move to the updated releases, which change the resolver to read installed package metadata instead of importing modules. Technical summary The flaw is an arbitrary module import issue in the ray_pkg_version OmegaConf resolver, which previously imported a module by name to read its __version__ attribute. The diff replaces that import with a lookup of installed distribution metadata via importlib.metadata, and the change notes say the resolver now takes distribution names rather than import names. Affected ranges are stated as 1.1.0.dev1 before 1.2.2 and 1.4.0.dev4 before 1.4.0rc2, with fixed versions 1.2.2 and 1.4.0rc2 implied by those ranges. The advisory does not state a CVSS score, attack preconditions, exploitation status, or a workaround beyond the migration guidance, and it gives no detection guidance. Users should replace import-style names such as yaml with distribution names such as PyYAML, and install packages (including editable installs) so their metadata is available. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/hydra-ecosystem/hydra/commit…16b1229bd1614b73d765 Impact if exploited ConfidentialityNone IntegrityLow AvailabilityNone How it is exploited Attack vector Local Attack complexity Low Attack requirements None Privileges required Low User interaction None CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/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 hydra-ecosystem hydra-ray-launcher hydra-ecosystem hydra-ray-launcher hydra-ray-launcher NIST National Vulnerability DatabasePublished Oct 23, 2026 13: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