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	Flags	Published
	Low	3.6	CVE-2026-106071	A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule. When the... OpenSSL, undici, Node.jsOpenSSL, undici, Node.js node, c-ares, SQLite, The Node.js Project Node.js	NVD		Oct 23 17:17 UTC
CVE-2026-106071A flaw in Node.js Permission Model filesystem enforcement can grant access to paths that do not match a wildcard `--allow-fs-read` or `--allow-fs-write` rule. When the... Executive summary This advisory covers a low-severity flaw in the Node.js Permission Model, which is meant to restrict file access for Node.js programs. The flaw affects Node.js 26.x and can let code read files outside a wildcard read rule, such as reading /etc/passwd when only /etc/passwd.* is granted. The advisory rates it LOW and points users to the Node.js 26.x security release, Node.js v26.12.1, which is listed alongside the other fixes. Technical summary The flaw is in Node.js Permission Model filesystem enforcement, where the radix tree lookup for wildcard --allow-fs-read or --allow-fs-write rules stops comparing early when the requested path is shorter than the grant prefix, so the path is treated as a match. The advisory says it requires a wildcard grant sitting directly under the root of the permission tree, for example when it is the only grant for that scope, and that the attacker needs code running under --permission. It affects Node.js 26.x only. The advisory does not state a fixed version specifically for this CVE, though it lists Node.js v26.12.1 as the release for the 26.x line. No workaround, exploitation status, CVSS score, or detection guidance is stated. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from nodejs.org/en/blog/vulnerability/octobe…26-security-releases Impact if exploited ConfidentialityLow IntegrityLow AvailabilityNone How it is exploited Attack vector Local Attack complexity High Privileges required Low User interaction None Scope Unchanged CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N Affects OpenSSL undici Node.js c-ares SQLite The Node.js Project OpenSSL undici Node.js node c-ares SQLite The Node.js Project Node.js NIST National Vulnerability DatabasePublished Oct 23, 2026 17: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