Monthly
Catalyst::Seal before 0.03 memoises how a request path resolved using the path alone as the cache key, so an unauthenticated GET to a path whose action is declared POST-only poisons that entry and permanently disables the route for every later request in the same Perl process, including the legitimate POST. Where a POST-only action sits below a shallower action on the same path, a priming GET memoises the shallow route and a subsequent POST is dispatched there, skipping the deeper controller's auto() authorization guard. Exploitation requires a Catalyst application that has installed this non-default module; no public exploit has been identified at time of analysis and EPSS is low at 0.35% (26th percentile), while our independent assessment revises the impact down from the vendor-reported C:H/I:H/A:H to C:L/I:L/A:L (unauth., AV:N/AC:L/PR:N/UI:N/S:U), reflecting functional denial plus a possibility of an authorization check not running rather than a full compromise.
Hash collision exploitation in NVIDIA Dynamo's multimodal embedding cache on Linux allows unauthenticated remote attackers to corrupt cached inference data by submitting specially crafted images. The cache fails to incorporate image dimensions into its hash function, meaning two images with identical pixel byte sequences but different spatial dimensions resolve to the same cache key, causing the wrong embedding to be served for subsequent requests. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog, but the CVSS score of 7.5 with no authentication requirement (PR:N) elevates its priority in deployments where the inference API is network-accessible.
Tunnel decapsulation logic in Arista EOS fails to verify the encapsulation protocol type, allowing any tunneled packet destined for a configured decapsulation IP to be silently unwrapped and forwarded into the network. Unauthenticated remote attackers (PR:N, AV:N per CVSS 4.0) can inject traffic into network segments by exploiting this check bypass on switches with VXLAN, decap-groups, or GRE configurations. The CVE description explicitly states this issue has been reported as exploited in the wild; however, a CISA KEV entry was not confirmed in the provided data. The integrity impact is assessed as low on both the vulnerable and subsequent systems per CVSS 4.0 (VI:L/SI:L), but the network trust boundary violation in a core switching context warrants elevated operational priority.
The jsrsasign JavaScript cryptographic library contains a critical vulnerability in its random number generation functions that allows attackers to recover private DSA keys through nonce bias exploitation. Versions 7.0.0 through 11.1.0 are affected. A proof-of-concept is publicly available (referenced in GitHub Gist), demonstrating the attack feasibility, and the vulnerability requires no authentication or user interaction for remote exploitation.
Risk assessment is currently not possible for CVE-2026-91768, an Ubuntu-tracked identifier that arrives with no description, no CVSS score, no CVSS vector, no CWE classification, and no CPE data; the only signal available is that the record was reported by the Ubuntu vendor source. Because attack vector, privileges required, user interaction, and affected package or deployment mode are all unspecified, no meaningful statement can be made about what an attacker could do or who is exposed. Exploitation status is unconfirmed: no public exploit identified at time of analysis, and there is no KEV listing, no EPSS score, and no proof-of-concept reference in the supplied intelligence. Security teams should treat this identifier as un-triageable and hold it in a watch state until the Ubuntu CVE tracker or the NVD/MITRE record supplies a description and affected package.
Incomplete comparison logic in OpenClaw ClawScan's built-in static scanner (internal/runner/static_scanner.go) through version 0.1.6 lets packaged Python bytecode slip past the deterministic text scan, so malicious skills or OpenClaw plugins can pass inspection undetected. The vendor fix in v0.1.7 (commit 9f6a6fbb9f1137345566d0ab44c73893dfe112fa, PR #41) explicitly adds flagging of packaged Python bytecode as opaque executable content. A publicly available exploit (GitHub issue #40) demonstrates the bypass, but the flaw is local-only, requires a low-privileged local user plus passive user interaction, and yields only a low integrity impact (CVSS 4.0 base 0.9).
Job deduplication in the cakephp/queue plugin can be bypassed by attackers who control job parameter data, causing legitimate unique jobs to be silently dropped. The flaw affects all applications using `shouldBeUnique = true` on job classes where user-supplied input is passed as job parameters - versions 0.1.10 through 2.3.0. No public exploit identified at time of analysis, and the CVSS score of 3.7 (AV:N/AC:H) reflects that exploitation requires knowledge of the target application's job parameter schema.
Hostname blocklist bypass in OpenClaw before 2026.5.26 enables authenticated attackers to reach operator-restricted network destinations by supplying trailing-dot notation in model- or workspace-derived URLs. The comparison logic evaluating hostnames against blocklist policies does not normalize fully qualified domain name (FQDN) trailing dots before evaluation, while DNS resolvers treat `blocked.example.com.` and `blocked.example.com` as identical targets. With confidentiality impact rated High by CVSS 4.0 and no public exploit or KEV listing identified at time of analysis, risk is real but bounded to deployments with active blocklist policies and users who control URL parameters.
OpenClaw's retry endpoint authentication check performs hostname prefix matching instead of exact hostname comparison, enabling an authenticated attacker to redirect sensitive authentication material to an attacker-controlled endpoint. All versions before 2026.5.7 are affected per CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*. The CVSS 4.0 vector scores this at 6.0 with high confidentiality impact (VC:H) and a specific attack prerequisite (AT:P); no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Cache-bypass information disclosure in Django's `has_vary_header()` utility allows remote attackers to read cached HTTP responses intended for other users by exploiting improper whitespace handling in `Vary` header comparisons. Affected versions are Django 5.2.x before 5.2.15 and 6.0.x before 6.0.6; earlier unsupported series (5.0.x, 4.1.x, 3.2.x) were not evaluated and may also be affected per the vendor. The CVSS 4.0 score of 2.3 reflects constrained real-world impact requiring both a non-default prerequisite condition and user interaction, with no public exploit or confirmed active exploitation identified at time of analysis.
Catalyst::Seal before 0.03 memoises how a request path resolved using the path alone as the cache key, so an unauthenticated GET to a path whose action is declared POST-only poisons that entry and permanently disables the route for every later request in the same Perl process, including the legitimate POST. Where a POST-only action sits below a shallower action on the same path, a priming GET memoises the shallow route and a subsequent POST is dispatched there, skipping the deeper controller's auto() authorization guard. Exploitation requires a Catalyst application that has installed this non-default module; no public exploit has been identified at time of analysis and EPSS is low at 0.35% (26th percentile), while our independent assessment revises the impact down from the vendor-reported C:H/I:H/A:H to C:L/I:L/A:L (unauth., AV:N/AC:L/PR:N/UI:N/S:U), reflecting functional denial plus a possibility of an authorization check not running rather than a full compromise.
Hash collision exploitation in NVIDIA Dynamo's multimodal embedding cache on Linux allows unauthenticated remote attackers to corrupt cached inference data by submitting specially crafted images. The cache fails to incorporate image dimensions into its hash function, meaning two images with identical pixel byte sequences but different spatial dimensions resolve to the same cache key, causing the wrong embedding to be served for subsequent requests. No public exploit code has been identified and this vulnerability is not listed in the CISA KEV catalog, but the CVSS score of 7.5 with no authentication requirement (PR:N) elevates its priority in deployments where the inference API is network-accessible.
Tunnel decapsulation logic in Arista EOS fails to verify the encapsulation protocol type, allowing any tunneled packet destined for a configured decapsulation IP to be silently unwrapped and forwarded into the network. Unauthenticated remote attackers (PR:N, AV:N per CVSS 4.0) can inject traffic into network segments by exploiting this check bypass on switches with VXLAN, decap-groups, or GRE configurations. The CVE description explicitly states this issue has been reported as exploited in the wild; however, a CISA KEV entry was not confirmed in the provided data. The integrity impact is assessed as low on both the vulnerable and subsequent systems per CVSS 4.0 (VI:L/SI:L), but the network trust boundary violation in a core switching context warrants elevated operational priority.
The jsrsasign JavaScript cryptographic library contains a critical vulnerability in its random number generation functions that allows attackers to recover private DSA keys through nonce bias exploitation. Versions 7.0.0 through 11.1.0 are affected. A proof-of-concept is publicly available (referenced in GitHub Gist), demonstrating the attack feasibility, and the vulnerability requires no authentication or user interaction for remote exploitation.
Risk assessment is currently not possible for CVE-2026-91768, an Ubuntu-tracked identifier that arrives with no description, no CVSS score, no CVSS vector, no CWE classification, and no CPE data; the only signal available is that the record was reported by the Ubuntu vendor source. Because attack vector, privileges required, user interaction, and affected package or deployment mode are all unspecified, no meaningful statement can be made about what an attacker could do or who is exposed. Exploitation status is unconfirmed: no public exploit identified at time of analysis, and there is no KEV listing, no EPSS score, and no proof-of-concept reference in the supplied intelligence. Security teams should treat this identifier as un-triageable and hold it in a watch state until the Ubuntu CVE tracker or the NVD/MITRE record supplies a description and affected package.
Incomplete comparison logic in OpenClaw ClawScan's built-in static scanner (internal/runner/static_scanner.go) through version 0.1.6 lets packaged Python bytecode slip past the deterministic text scan, so malicious skills or OpenClaw plugins can pass inspection undetected. The vendor fix in v0.1.7 (commit 9f6a6fbb9f1137345566d0ab44c73893dfe112fa, PR #41) explicitly adds flagging of packaged Python bytecode as opaque executable content. A publicly available exploit (GitHub issue #40) demonstrates the bypass, but the flaw is local-only, requires a low-privileged local user plus passive user interaction, and yields only a low integrity impact (CVSS 4.0 base 0.9).
Job deduplication in the cakephp/queue plugin can be bypassed by attackers who control job parameter data, causing legitimate unique jobs to be silently dropped. The flaw affects all applications using `shouldBeUnique = true` on job classes where user-supplied input is passed as job parameters - versions 0.1.10 through 2.3.0. No public exploit identified at time of analysis, and the CVSS score of 3.7 (AV:N/AC:H) reflects that exploitation requires knowledge of the target application's job parameter schema.
Hostname blocklist bypass in OpenClaw before 2026.5.26 enables authenticated attackers to reach operator-restricted network destinations by supplying trailing-dot notation in model- or workspace-derived URLs. The comparison logic evaluating hostnames against blocklist policies does not normalize fully qualified domain name (FQDN) trailing dots before evaluation, while DNS resolvers treat `blocked.example.com.` and `blocked.example.com` as identical targets. With confidentiality impact rated High by CVSS 4.0 and no public exploit or KEV listing identified at time of analysis, risk is real but bounded to deployments with active blocklist policies and users who control URL parameters.
OpenClaw's retry endpoint authentication check performs hostname prefix matching instead of exact hostname comparison, enabling an authenticated attacker to redirect sensitive authentication material to an attacker-controlled endpoint. All versions before 2026.5.7 are affected per CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*. The CVSS 4.0 vector scores this at 6.0 with high confidentiality impact (VC:H) and a specific attack prerequisite (AT:P); no public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV.
Cache-bypass information disclosure in Django's `has_vary_header()` utility allows remote attackers to read cached HTTP responses intended for other users by exploiting improper whitespace handling in `Vary` header comparisons. Affected versions are Django 5.2.x before 5.2.15 and 6.0.x before 6.0.6; earlier unsupported series (5.0.x, 4.1.x, 3.2.x) were not evaluated and may also be affected per the vendor. The CVSS 4.0 score of 2.3 reflects constrained real-world impact requiring both a non-default prerequisite condition and user interaction, with no public exploit or confirmed active exploitation identified at time of analysis.