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
	High	8.9	CVE-2026-115729	@pdfme/common from 5.5.10 before 6.2.6 contains a server-side request forgery vulnerability that allows attackers to bypass the isUrlSafeToFetch denylist in getB64BasePdf pdfmepdfme common	NVD		Oct 23 13:17 UTC
CVE-2026-115729@pdfme/common from 5.5.10 before 6.2.6 contains a server-side request forgery vulnerability that allows attackers to bypass the isUrlSafeToFetch denylist in getB64BasePdf Executive summary The advisory says @pdfme/common versions from 5.5.10 before 6.2.6 contain a server-side request forgery flaw that lets attackers bypass the URL safety check used when fetching base PDF templates. An attacker could use this to make the server request internal or otherwise restricted addresses. The advisory's diff shows the fix is a stricter URL check, and it does not state a severity rating. Technical summary The flaw is a server-side request forgery (SSRF) in the getB64BasePdf function, where the isUrlSafeToFetch denylist can be bypassed through alternative IP address notations and IPv6 forms such as IPv4-mapped, NAT64, and 6to4 addresses. The advisory states the affected range as 5.5.10 before 6.2.6 and the fix appears in 6.2.6 per the version range, though the advisory does not explicitly name a fixed version beyond that range. The diff replaces the old checks with a parser that validates IPv4 and IPv6 literals against non-public ranges and rejects loopback hostnames, and its code comment notes that DNS names resolving to internal addresses and redirects are not covered. Attack vector details such as required privileges and user interaction are not stated, and no CVSS score is stated. No workarounds or detection guidance are stated beyond the code comment about server-side validation of untrusted templates. Summaries are generated by AI from the linked advisory text. Confirm versions and fixes at the source. Summarized from github.com/pdfme/pdfme/commit/d03d0bc49…2879793c5ff52c5600a6 Impact if exploited ConfidentialityHigh IntegrityNone AvailabilityNone 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:N/VA:N/SC:H/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 pdfme pdfme common 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