PT-2026-65397

The Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.3.7. This is due to missing or incorrect nonce validation on the process bulk action function. This makes it possible for unauthenticate...

CVE-2026-15136: Cross-Site Request Forgery (CSRF)

The Cookie Banner for GDPR / CCPA – WPLP Cookie Consent plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.3.7. This is due to missing or incorrect nonce validation on the processbulkaction function. This makes it possible for unauthenticated...

CVE-2026-64746

An authorization issue was addressed with improved validation. This issue is fixed in iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6 and iPadOS 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6. An app may be able to add contacts without user authorization...

CVE-2026-64746

An authorization issue was addressed with improved validation. This issue is fixed in iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6 and iPadOS 26.6, macOS Tahoe 26.6, visionOS 26.6, watchOS 26.6. An app may be able to add contacts without user authorization...

WordPress WPLP Cookie Consent – Cookie Banner & Consent Management for GDPR, CCPA & Google Consent Mode plugin <= 4.3.7 - Cross-Site Request Forgery vulnerability

Cross-Site Request Forgery vulnerability discovered by Wordfence PRISM in WordPress Plugin WP Cookie Notice for GDPR, CCPA & ePrivacy Consent versions = 4.3.7...

OpenAM Reflected XSS in the OAuth2/OIDC `wap` consent page

Description The OAuth2/OIDC consent page rendered for display=wap authorize requests reflected several request-derived values into the HTML response without escaping. An attacker who induces a user with an active OpenAM session to follow a crafted authorize link can execute arbitrary JavaScript i...

Cross-site Scripting (XSS)

Overview Affected versions of this package are vulnerable to Cross-site Scripting XSS via the wap/authorize.ftl consent template in the OAuth2/OIDC consent page. An attacker can execute arbitrary JavaScript in the OpenAM origin by sending a victim with an active session a crafted display=wap...

GHSA-VQXV-6XRH-49CP OpenAM Reflected XSS in the OAuth2/OIDC `wap` consent page

Description The OAuth2/OIDC consent page rendered for display=wap authorize requests reflected several request-derived values into the HTML response without escaping. An attacker who induces a user with an active OpenAM session to follow a crafted authorize link can execute arbitrary JavaScript i...

PT-2026-64445

Name of the Vulnerable Software and Affected Versions Open Access Management OpenAM versions 13.0.0 through 16.1.1 Description The OAuth2 authorize endpoint's consent page, when using display=wap, reflects request-derived values through ConsentRequiredResource and wap/authorize.ftl without proper...

Incorrect Authorization

Overview Affected versions of this package are vulnerable to Incorrect Authorization in the OAuth 2.1 authorization. An attacker can gain unauthorized access to another user's workflow and execute it with the owner's credentials by registering an OAuth client and self-approving consent for a...

CVE-2026-65594 n8n before 2.30.1 Missing OAuth Authorization Check

n8n before 2.29.8 and 2.30.x before 2.30.1 affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger...

CVE-2026-65594

n8n before 2.29.8 and 2.30.x before 2.30.1 affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger...

CVE-2026-65594

n8n (versions affected: before 2.29.8 and 2.30.x before 2.30.1; affected since 2.27.0) has an OAuth 2.1 flow where authentication does not verify that the user has access to the referenced workflow used as the OAuth resource. On systems with an active MCP Server Trigger workflow configured for n8...

PT-2026-63352

n8n before 2.29.8 and 2.30.x before 2.30.1 affected from 2.27.0, when the OAuth 2.1 consent and token-issuance flow was introduced does not verify that the authenticated user has access to the workflow referenced as the OAuth resource. On instances with at least one active MCP Server Trigger...

The vulnerability of the Unified Consent System component in Windows operating systems, which allows a violator to increase their privileges

The vulnerability of the Unified Consent System component in Windows operating systems relates to the possibility of exploiting memory after it is freed. Exploiting this vulnerability could allow an attacker to increase their privileges...

Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass

Impact Envoy Gateway accepts extension-managed custom backendRefs from an HTTPRoute to a backend resource in another namespace without requiring a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model: the namespace that owns the...

GHSA-FCRP-7GC2-93G7 Envoy Gateway custom backendRef cross-namespace ReferenceGrant bypass

Impact Envoy Gateway accepts extension-managed custom backendRefs from an HTTPRoute to a backend resource in another namespace without requiring a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model: the namespace that owns the...

Samsung backs down on threat to delete health data

If you pay for something, you expect it to work as intended. The vendor shouldn't start turning features off just because you won't accept its new rules. Someone should tell Samsung, which just upset users of its health app by threatening exactly that—before changing course after a user backlash...

PT-2026-60664

Impact Envoy Gateway accepts extension-managed custom backendRefs from an HTTPRoute to a backend resource in another namespace without requiring a matching Gateway API ReferenceGrant in the target namespace. This breaks the Gateway API cross-namespace consent model: the namespace that owns the...

PT-2026-60690

Name of the Vulnerable Software and Affected Versions Envoy Gateway versions prior to 1.7.4 Envoy Gateway versions prior to 1.8.1 Description Envoy Gateway allows extension-managed custom backendRefs from an HTTPRoute to a backend resource in a different namespace without requiring a correspondin...