Monthly
Broken object-level authorization in the Wheels (CFML) framework 4.0.0 through 4.1.2 lets an authenticated low-privilege attacker supply a record key to findByKey(), exists(key=), updateByKey(), or deleteByKey() and have the framework drop the application's scope condition (such as a tenant or owner filter), enabling read, modification, or deletion of another user's or tenant's record. The flaw is remotely exploitable (AV:N, PR:L, no user interaction) with high confidentiality and integrity impact but no availability impact, and the exists(key=) variant additionally leaks record existence by returning true for an out-of-scope key when the application runs in production mode with error information disabled. No public exploit code or CISA KEV entry is identified at time of analysis, and exploitation requires an application that relies on Wheels scopes for ownership or tenant authorization and passes request-supplied keys into the affected methods.
Information disclosure in Backdrop CMS Core's token browser allows authenticated users to enumerate available token types, though individual token names remain protected. The flaw affects versions 1.34.x before 1.34.6 and 1.35.x before 1.35.2. No public exploit has been identified, and vendor patches are available.
OpenSSH sshd before 10.6 can incorrectly persist GSSAPIAuthentication state across authentication attempts when GSSAPIAuthentication is enabled, allowing a remote, unauthenticated attacker to influence authentication integrity on the same connection. This is a non-default configuration issue: stock OpenSSH deployments without Kerberos/GSSAPI are not affected, and the attacker must drive a sequence of authentication attempts (high attack complexity). No public exploit code has been identified, EPSS is very low (0.08%, 0th percentile), and CISA SSVC reports no exploitation; the vendor has released a fix in OpenSSH 10.6.
Credentials can incorrectly persist after a failed GSSAPIAuthentication attempt in the sshd daemon of OpenSSH before 10.6, allowing an authentication context that should have been discarded to remain usable and potentially granting access under another identity (CWE-669, integrity impact). Only hosts that explicitly enable GSSAPIAuthentication are affected, since the OpenSSH default is 'no', so exposure is largely limited to Kerberos/GSSAPI-integrated environments; the flaw is fixed in OpenSSH 10.6. No public exploit code has been identified at time of analysis, EPSS is negligible (0.08%), and CISA SSVC records no observed exploitation and rates the issue as non-automatable with partial technical impact, so real-world risk is moderate despite the 7.5 'High' base score.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
Local privilege escalation to root in Pexip Infinity (versions before 38.2, plus 39.0, 39.1, and 40.0) allows an attacker who already holds a foothold on a node to break out of a low-privileged local context and obtain full root control. Per the CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), the flaw is local-only, requires low privileges, and is not remotely exploitable on its own: the attacker must first run arbitrary code on the node, either by chaining a separate remote code execution vulnerability or by already possessing administrative access to the node's operating system. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the practical risk is that this bug turns any successful initial compromise of a Pexip Infinity host into a complete root compromise, so it should be treated as a meaningful post-exploitation escalation rather than a standalone remote threat.
vm2 versions 3.11.4 through 3.11.6 allow untrusted JavaScript running inside the sandbox to bypass cross-realm registered-symbol filtering and write Node.js internal stream symbols onto host WebStream objects, corrupting host-visible stream state - for example making stream.Readable.isDisturbed() return false for an already-consumed stream, which can defeat host logic that enforces one-shot body consumption or rejects errored streams. Exploitation is unauthenticated per the CVSS vector (PR:N) but requires a non-default setup: the embedder must expose both a host WebStream object and the host stream/web module to sandboxed code, and the host must run a Node.js release that exposes nodejs.stream.disturbed and nodejs.stream.errored on WebStream prototypes (validated on Node.js v25.8.0). Impact is integrity-only, with no host code execution, confidentiality, or availability loss in the reported proof; no public exploit code has been identified at time of analysis, and the flaw is fixed in vm2 3.11.7.
Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) contain multiple internally discovered vulnerabilities grouped under CVE-2026-20194, stemming from incorrect resource transfer between spheres (CWE-669). An authenticated attacker with high privileges can exploit these over the network to potentially achieve high confidentiality, integrity, and availability impact, as reflected by the CVSS 3.1 score of 9.1 (Critical) with scope change. No public exploit code or active exploitation has been identified at time of analysis, and the high-privilege authentication prerequisite confines realistic risk to trusted insiders or attackers who already hold administrative access.
SSRF, XXE and denial of service exposure arise in libxml2 before 2.15.4 because xmlXIncludeProcess and xmlXIncludeProcessTree fail to propagate the document's parseFlags down to the parser contexts they create for XInclude resolution. When parseFlags are dropped, protective options such as XML_PARSE_NONET stop being enforced, so an attacker-supplied document containing an external xi:include href can force outbound network fetches through the application's resource loader — enabling server-side request forgery, external entity injection, or a hang driven by an intentionally slow remote resource. Exploitation requires an application that enables XInclude and relies on XML_PARSE_NONET (typically with a custom resource loader); no public exploit code has been identified and EPSS is very low at 0.16% (6th percentile), with no CISA KEV listing.
Remote content blocking evasion in Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3 lets a crafted SVG image with an unclosed url() in a FuncIRI attribute slip past the remote-image blocker, so external resources load when a victim views a malicious email. This exposes the recipient's IP, mail-client fingerprint, and email-open telemetry to the sender, and per the advisory may aid further information disclosure or privilege escalation. It has a vendor patch and no public exploit identified at time of analysis; EPSS is low (0.31%) and CISA SSVC rates exploitation as none.
Broken object-level authorization in the Wheels (CFML) framework 4.0.0 through 4.1.2 lets an authenticated low-privilege attacker supply a record key to findByKey(), exists(key=), updateByKey(), or deleteByKey() and have the framework drop the application's scope condition (such as a tenant or owner filter), enabling read, modification, or deletion of another user's or tenant's record. The flaw is remotely exploitable (AV:N, PR:L, no user interaction) with high confidentiality and integrity impact but no availability impact, and the exists(key=) variant additionally leaks record existence by returning true for an out-of-scope key when the application runs in production mode with error information disabled. No public exploit code or CISA KEV entry is identified at time of analysis, and exploitation requires an application that relies on Wheels scopes for ownership or tenant authorization and passes request-supplied keys into the affected methods.
Information disclosure in Backdrop CMS Core's token browser allows authenticated users to enumerate available token types, though individual token names remain protected. The flaw affects versions 1.34.x before 1.34.6 and 1.35.x before 1.35.2. No public exploit has been identified, and vendor patches are available.
OpenSSH sshd before 10.6 can incorrectly persist GSSAPIAuthentication state across authentication attempts when GSSAPIAuthentication is enabled, allowing a remote, unauthenticated attacker to influence authentication integrity on the same connection. This is a non-default configuration issue: stock OpenSSH deployments without Kerberos/GSSAPI are not affected, and the attacker must drive a sequence of authentication attempts (high attack complexity). No public exploit code has been identified, EPSS is very low (0.08%, 0th percentile), and CISA SSVC reports no exploitation; the vendor has released a fix in OpenSSH 10.6.
Credentials can incorrectly persist after a failed GSSAPIAuthentication attempt in the sshd daemon of OpenSSH before 10.6, allowing an authentication context that should have been discarded to remain usable and potentially granting access under another identity (CWE-669, integrity impact). Only hosts that explicitly enable GSSAPIAuthentication are affected, since the OpenSSH default is 'no', so exposure is largely limited to Kerberos/GSSAPI-integrated environments; the flaw is fixed in OpenSSH 10.6. No public exploit code has been identified at time of analysis, EPSS is negligible (0.08%), and CISA SSVC records no observed exploitation and rates the issue as non-automatable with partial technical impact, so real-world risk is moderate despite the 7.5 'High' base score.
Incorrect resource transfer between spheres in the NVIDIA vGPU Virtual GPU Manager for Linux allows a locally positioned, low-privileged attacker to break an internal resource-handling boundary and gain high-integrity impact - code execution, privilege escalation, data tampering, information disclosure, or denial of service on the host running the vGPU Manager. This affects virtualization/vGPU deployments on Linux (the manager component on the hypervisor host), not standard desktop GPU drivers, and the CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) confirms the attacker must already hold local low-privileged access to a context served by that manager, such as a guest VM or a local account on the host; there is no network or unauthenticated path. It is a genuine local privilege-escalation class issue rather than a remotely triggerable one, and no public exploit was identified at time of analysis.
Local privilege escalation to root in Pexip Infinity (versions before 38.2, plus 39.0, 39.1, and 40.0) allows an attacker who already holds a foothold on a node to break out of a low-privileged local context and obtain full root control. Per the CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8), the flaw is local-only, requires low privileges, and is not remotely exploitable on its own: the attacker must first run arbitrary code on the node, either by chaining a separate remote code execution vulnerability or by already possessing administrative access to the node's operating system. There is no public exploit identified at time of analysis and no confirmed active exploitation (not in CISA KEV); the practical risk is that this bug turns any successful initial compromise of a Pexip Infinity host into a complete root compromise, so it should be treated as a meaningful post-exploitation escalation rather than a standalone remote threat.
vm2 versions 3.11.4 through 3.11.6 allow untrusted JavaScript running inside the sandbox to bypass cross-realm registered-symbol filtering and write Node.js internal stream symbols onto host WebStream objects, corrupting host-visible stream state - for example making stream.Readable.isDisturbed() return false for an already-consumed stream, which can defeat host logic that enforces one-shot body consumption or rejects errored streams. Exploitation is unauthenticated per the CVSS vector (PR:N) but requires a non-default setup: the embedder must expose both a host WebStream object and the host stream/web module to sandboxed code, and the host must run a Node.js release that exposes nodejs.stream.disturbed and nodejs.stream.errored on WebStream prototypes (validated on Node.js v25.8.0). Impact is integrity-only, with no host code execution, confidentiality, or availability loss in the reported proof; no public exploit code has been identified at time of analysis, and the flaw is fixed in vm2 3.11.7.
Cisco Identity Services Engine (ISE) and ISE Passive Identity Connector (ISE-PIC) contain multiple internally discovered vulnerabilities grouped under CVE-2026-20194, stemming from incorrect resource transfer between spheres (CWE-669). An authenticated attacker with high privileges can exploit these over the network to potentially achieve high confidentiality, integrity, and availability impact, as reflected by the CVSS 3.1 score of 9.1 (Critical) with scope change. No public exploit code or active exploitation has been identified at time of analysis, and the high-privilege authentication prerequisite confines realistic risk to trusted insiders or attackers who already hold administrative access.
SSRF, XXE and denial of service exposure arise in libxml2 before 2.15.4 because xmlXIncludeProcess and xmlXIncludeProcessTree fail to propagate the document's parseFlags down to the parser contexts they create for XInclude resolution. When parseFlags are dropped, protective options such as XML_PARSE_NONET stop being enforced, so an attacker-supplied document containing an external xi:include href can force outbound network fetches through the application's resource loader — enabling server-side request forgery, external entity injection, or a hang driven by an intentionally slow remote resource. Exploitation requires an application that enables XInclude and relies on XML_PARSE_NONET (typically with a custom resource loader); no public exploit code has been identified and EPSS is very low at 0.16% (6th percentile), with no CISA KEV listing.
Remote content blocking evasion in Roundcube Webmail before 1.6.18 and 1.7.x before 1.7.3 lets a crafted SVG image with an unclosed url() in a FuncIRI attribute slip past the remote-image blocker, so external resources load when a victim views a malicious email. This exposes the recipient's IP, mail-client fingerprint, and email-open telemetry to the sender, and per the advisory may aid further information disclosure or privilege escalation. It has a vendor patch and no public exploit identified at time of analysis; EPSS is low (0.31%) and CISA SSVC rates exploitation as none.