Vulnerability feed

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

Critical in the last 24 hours

1603 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

144-76% vs 7-day avg of 597

2 critical, 38 high, 59 medium, 25 low

Expand	Severity	Score	Advisory	Title	Source	Published
	Critical	9.4	CVE-2026-115557	Python has added a denylist for known compromised certificates to the "ssl" module to ensure user safety even without certificate revocation configured Python, GoPython CPython, Go, Go crypto/x509	NVD	Oct 24 15:17 UTC
CVE-2026-115557Python has added a denylist for known compromised certificates to the "ssl" module to ensure user safety even without certificate revocation configured Executive summary The advisory covers a Go security fix that blocks trust in a small set of intermediate certificates from a specific Certificate Authority, delivered in Go 1.27.3 and Go 1.26.10. The Go team says it highly recommends immediately upgrading to these releases. The advisory does not state how severe the issue is. Technical summary The fix is in crypto/x509 and is described as a mitigation for security concerns with a specific Certificate Authority. Verify now filters out certificate chains that contain a small set of named intermediate certificates, so they are not returned to the caller. The advisory is tagged CVE-2026-111943 and references Go issue 82345. The attack vector, preconditions, and exploitation status are not stated. The affected version range is not stated, and no CVSS score is given. No workaround or detection guidance is stated beyond upgrading to Go 1.27.3 or Go 1.26.10. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from openwall.com/lists/oss-security/2026/10/20/29 Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityHigh How it is exploited Attack vector Network Attack complexity Low Attack requirements None Privileges required None User interaction Passive CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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 Python Go Python CPython Go Go crypto/x509 NIST National Vulnerability DatabasePublished Oct 24, 2026 15:17 UTC Read the advisory
	Medium	6.9	CVE-2026-114583	tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended... PythonPython CPython, Python tarfile	NVD	Oct 22 21:17 UTC
CVE-2026-114583tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended... Executive summary The advisory describes a flaw in Python's tarfile module, specifically the tar_filter extraction filter, which could be bypassed with crafted link entries so that later archive members are redirected outside the intended destination directory. The advisory text does not state a severity rating or CVSS score. The fix adds a check so tar_filter rejects link members that refer to the destination directory itself. Technical summary The weakness is a path traversal issue in tarfile.tar_filter, reached by crafted link entries, including symlinks or hard links with empty or directory-like names, that can redirect later archive members outside the destination. The attack requires a victim to extract a crafted tar archive using the tar_filter extraction filter. The change adds a check that raises OutsideDestinationError for hard or soft link members whose normalized name is the current directory, and the previous destination-equals check was moved and applied to the tar filter as well as the data filter. The advisory does not state affected version ranges or fixed version numbers, and it does not state any workaround. No detection guidance is stated, and it is not stated whether exploitation has been observed in the wild. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/python/cpython/commit/04d8fc…1fec8a53a1330c3b665d Impact if exploited ConfidentialityNone IntegrityHigh AvailabilityNone How it is exploited Attack vector Local Attack complexity Low Attack requirements None Privileges required None User interaction None CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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 Python Python CPython Python tarfile NIST National Vulnerability DatabasePublished Oct 22, 2026 21:17 UTC Read the advisory
	High	7.6	CVE-2026-19553	ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set PythonPython CPython	NVD	Sep 30 17:16 UTC
CVE-2026-19553ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set From the advisory ssl.SSLContext.wrap_bio() didn't require the server_hostname argument to not be None if ssl.SSLContext.check_hostname was set. Due to a missing parameter check in SSLObject, if the server_hostname argument isn't supplied then hostname verification would be silently skipped. This defect could lead to programs where certificate hostname verification appeared to be succeeding with SSLContext.check_hostname = True and no ValueError being raised due to misconfiguration. If the program passes a server_hostname value that isn't an empty string or None to any of these APIs then certificate hostname verification proceeds as expected and the program is not affected by this vulnerability. Mitigating this vulnerability doesn't require updating Python or applying the patch. To mitigate, pass a valid non-None and non-empty server_hostname value to SSLContext.wrap_bio(), asyncio.create_connection(), or asyncio.loop.start_tls() and certificate hostname verification will proceed as expected. Upgrading to the latest version of Python or applying the patch only changes the behavior from silently skipping hostname verification to raising a ValueError, similar to SSLContext.wrap_socket(), when server_hostname isn't supplied. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityNone How it is exploited Attack vector Network Attack complexity Low Attack requirements Present Privileges required None User interaction Passive CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/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 Python Python CPython NIST National Vulnerability DatabasePublished Sep 30, 2026 17:16 UTC Read the advisory
	Critical	9.2	CVE-2026-19445	A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the... PythonPython CPython	NVD	Sep 30 17:16 UTC
CVE-2026-19445A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the... From the advisory A remote, unauthenticated TLS client can make a server crash or call through a freed pointer if its sni_callback assigns a different context to SSLSocket.context (the documented way to select a certificate per server name) and nothing else keeps the original ssl.SSLContext alive. Typical cases are servers that create an SSLContext per connection or replace it while connections are open; servers that wrap their listening socket with it are not affected. Mitigation: keep a reference to every SSLContext that sets sni_callback for the lifetime of the server. TLS clients are not affected. Impact if exploited ConfidentialityHigh IntegrityHigh AvailabilityLow How it is exploited Attack vector Network Attack complexity High Attack requirements Present Privileges required None User interaction None CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/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 Python Python CPython NIST National Vulnerability DatabasePublished Sep 30, 2026 17:16 UTC Read the advisory
	Medium	5.9	CVE-2026-12345	The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition PythonPython CPython	NVD	Sep 29 18:17 UTC
CVE-2026-12345The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition From the advisory The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags reset, with the privileges of the process performing the cleanup. Note that platforms where shutil.rmtree.avoids_symlink_attacks is false, remain affected, and file flags may still be reset outside of the tree on all platforms. Impact if exploited ConfidentialityNone IntegrityHigh AvailabilityHigh How it is exploited Attack vector Local Attack complexity Low Attack requirements Present Privileges required None User interaction None CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/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 Python Python CPython NIST National Vulnerability DatabasePublished Sep 29, 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

Executive summary

Technical summary

Impact if exploited

How it is exploited

Affects

From the advisory

Impact if exploited

How it is exploited

Affects

From the advisory

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