Monthly
Authorization bypass in Apache Camel's camel-netty-http component allows remote unauthenticated attackers to reach protected routes by changing the case of characters in the request path so the security constraint no longer recognizes it while routing still dispatches to the endpoint. It affects Apache Camel 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1, with a CVSS score of 8.2; no public exploit identified at time of analysis.
Subresource Integrity checks in undici can be bypassed when fetch() integrity metadata uses an uppercase or mixed-case algorithm token, allowing an attacker who controls the response body to deliver bytes that do not match the pinned digest without an integrity error. The issue affects undici 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1 and is fixed in 7.30.1 and 8.12.2; exploitation requires both non-lowercase SRI token usage and attacker control of the HTTP response, and impact is integrity-only. No public exploit was identified at time of analysis, and EPSS is low at 0.25% (15th percentile), consistent with the assessed high attack complexity and limited real-world exposure.
Eclipse Jetty's host whitelist/blacklist enforcement in the jetty-server and jetty-proxy modules performs case-sensitive comparisons, so a remote, unauthenticated attacker can bypass the filter simply by altering the letter case of the Host value (e.g. 'EXAMPLE.com' instead of 'example.com') and reach hosts the operator intended to block or exclude. The flaw only matters where an operator has explicitly configured a host whitelist or blacklist and treats it as a security boundary; deployments without host-based filtering are unaffected. The vendor has published a security advisory (GHSA-7wfj-j486-mxrf), and no public exploit code has been identified at time of analysis, though the low attack complexity (AC:L, PR:N, UI:N) and high confidentiality impact make the bypass straightforward to attempt wherever the non-default filtering configuration is present.
Root-level command execution on the Wazuh Manager host is achievable by an authenticated administrator who holds the manager:update_config permission and submits an ossec.conf localfile block whose LOG_FORMAT keyword is spelled in uppercase. The case-sensitive configuration validator does not recognize the uppercase form as a remote-command directive and lets it pass, while wazuh-logcollector matches the keyword case-insensitively and therefore executes the embedded command as root the next time the configuration is reloaded. The flaw affects Wazuh 4.14.3 through 4.14.7 and is fixed in 4.14.8; no public exploit code has been identified at time of analysis, and the real-world risk is materially gated by the high-privilege (PR:H) prerequisite required to reach the vulnerable configuration path.
Privilege escalation in HashiCorp Vault and Vault Enterprise allows an authenticated principal with delegated permissions to bypass explicit deny ACL rules by referencing a resource or policy name in non-canonical form, potentially reaching a protected resource or assigning a denied policy. Affected are Vault Community Edition before 2.1.2 and Vault Enterprise before 2.1.2, 1.21.12, 1.20.17, and 1.19.23, rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires an already high-privileged, delegated user (PR:H) operating in a policy model that depends on explicit deny rules, and no public exploit code or confirmed active exploitation was identified at time of analysis (no EPSS data was provided), so this is best handled as a defense-in-depth hardening fix rather than an emergency.
Authenticated users of Backstage Scaffolder can bypass administrator-configured action restrictions in @backstage/plugin-scaffolder-backend by supplying a restricted input value with different letter casing or as a different JSON type (for example a number instead of a string), causing permission checks to fail to match and letting the action execute with the backend integration's credentials. This can grant unauthorized access to repositories and related source-control resources, bounded by the privileges of the integration tokens attached to the affected actions. The issue affects versions before 3.3.1, 3.4.1, 4.0.3, and 4.1.0, and only matters in deployments that actually use input-value-based permission rules; no public exploit code has been identified at time of analysis.
Case-sensitivity bypass in Hugo's security.http.urls IP-literal deny rule lets builds running v0.162.0 through v0.165.x fetch URLs that the rule was configured to block - a mixed-case scheme such as 'HTTP://localhost/...' evades the deny match, re-enabling SSRF through resources.GetRemote. The issue is unauthenticated (PR:N) but local (AV:L): it only matters when a Hugo build processes attacker-influenced input and the operator depends on the IP-literal deny rule as the SSRF control, and it cannot be triggered against an already-served static site. No public exploit code has been identified and there is no confirmation of active exploitation, but a vendor patch is available in Hugo v0.166.0.
Information disclosure in Grav CMS before 2.0.25 lets unauthenticated remote attackers read sensitive files - configuration secrets and account password hashes - when the site is served by Microsoft IIS using the bundled webserver-configs/web.config over a case-insensitive filesystem such as NTFS, simply by varying the case of a folder name or extension (for example GET /user/CONFIG/system.YAML) so that none of the case-sensitive URL Rewrite deny rules match. The practical blast radius is narrower than the raw path-bypass suggests: whether a bypassed file is actually returned depends on MIME registration, with .json served by default while .yaml/.yml return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added; the equivalent gap in webserver-configs/lighttpd.conf is lower risk because lighttpd typically runs on case-sensitive filesystems, and deployments behind Apache (.htaccess), nginx, Caddy, or the PHP built-in server are not affected. No public exploit identified at time of analysis, and while the vendor-released patch is Grav 2.0.25, upgrading alone is insufficient because the .htaccess installer heal does not rewrite web.config or lighttpd.conf, so operators must manually re-copy the corrected sample files.
OpenClaw (npm package 'openclaw') before 2026.7.1 lets an actor who can steer a tool-enabled agent create a persistent cron job that runs attacker-chosen commands with the privileges of the OpenClaw process user. A mixed-case payload 'kind' value slips past the agent-facing shell-execution guard and later normalizes into a command job, targeting the model-facing cron tool only. The vendor scores this 8.7 (High) on CVSS 4.0 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) and the vendor-released patch is 2026.7.1; no public exploit identified at time of analysis.
Authorization bypass in OpenClaw's Matrix integration (@openclaw/matrix) allows an authenticated Matrix participant to inherit another account's authority when their user identifier collides after case/Unicode folding. Versions 2026.2.2 through 2026.8.0 lowercase the complete Matrix user ID - including the case-sensitive server-name portion and historical localparts - before deriving the OpenClaw authorization identity, so an attacker controlling a protocol-valid, fold-equivalent identifier (display-name matching is not required) can gain allowlist, owner-command, exec-approval, or plugin-approval rights configured for the privileged account. The vendor rates this CVSS 7.7 with high confidentiality, integrity, and availability impact; real-world risk is moderate and gated by the attacker needing a valid authenticated Matrix account plus a registrable colliding identifier, and no public exploit identified at time of analysis.
Authorization bypass in Apache Camel's camel-netty-http component allows remote unauthenticated attackers to reach protected routes by changing the case of characters in the request path so the security constraint no longer recognizes it while routing still dispatches to the endpoint. It affects Apache Camel 4.0.0 before 4.18.5 and 4.19.0 before 4.22.1, with a CVSS score of 8.2; no public exploit identified at time of analysis.
Subresource Integrity checks in undici can be bypassed when fetch() integrity metadata uses an uppercase or mixed-case algorithm token, allowing an attacker who controls the response body to deliver bytes that do not match the pinned digest without an integrity error. The issue affects undici 7.15.0 through 7.30.0 and 8.0.0 through 8.12.1 and is fixed in 7.30.1 and 8.12.2; exploitation requires both non-lowercase SRI token usage and attacker control of the HTTP response, and impact is integrity-only. No public exploit was identified at time of analysis, and EPSS is low at 0.25% (15th percentile), consistent with the assessed high attack complexity and limited real-world exposure.
Eclipse Jetty's host whitelist/blacklist enforcement in the jetty-server and jetty-proxy modules performs case-sensitive comparisons, so a remote, unauthenticated attacker can bypass the filter simply by altering the letter case of the Host value (e.g. 'EXAMPLE.com' instead of 'example.com') and reach hosts the operator intended to block or exclude. The flaw only matters where an operator has explicitly configured a host whitelist or blacklist and treats it as a security boundary; deployments without host-based filtering are unaffected. The vendor has published a security advisory (GHSA-7wfj-j486-mxrf), and no public exploit code has been identified at time of analysis, though the low attack complexity (AC:L, PR:N, UI:N) and high confidentiality impact make the bypass straightforward to attempt wherever the non-default filtering configuration is present.
Root-level command execution on the Wazuh Manager host is achievable by an authenticated administrator who holds the manager:update_config permission and submits an ossec.conf localfile block whose LOG_FORMAT keyword is spelled in uppercase. The case-sensitive configuration validator does not recognize the uppercase form as a remote-command directive and lets it pass, while wazuh-logcollector matches the keyword case-insensitively and therefore executes the embedded command as root the next time the configuration is reloaded. The flaw affects Wazuh 4.14.3 through 4.14.7 and is fixed in 4.14.8; no public exploit code has been identified at time of analysis, and the real-world risk is materially gated by the high-privilege (PR:H) prerequisite required to reach the vulnerable configuration path.
Privilege escalation in HashiCorp Vault and Vault Enterprise allows an authenticated principal with delegated permissions to bypass explicit deny ACL rules by referencing a resource or policy name in non-canonical form, potentially reaching a protected resource or assigning a denied policy. Affected are Vault Community Edition before 2.1.2 and Vault Enterprise before 2.1.2, 1.21.12, 1.20.17, and 1.19.23, rated CVSS 3.1 7.2 (AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). Exploitation requires an already high-privileged, delegated user (PR:H) operating in a policy model that depends on explicit deny rules, and no public exploit code or confirmed active exploitation was identified at time of analysis (no EPSS data was provided), so this is best handled as a defense-in-depth hardening fix rather than an emergency.
Authenticated users of Backstage Scaffolder can bypass administrator-configured action restrictions in @backstage/plugin-scaffolder-backend by supplying a restricted input value with different letter casing or as a different JSON type (for example a number instead of a string), causing permission checks to fail to match and letting the action execute with the backend integration's credentials. This can grant unauthorized access to repositories and related source-control resources, bounded by the privileges of the integration tokens attached to the affected actions. The issue affects versions before 3.3.1, 3.4.1, 4.0.3, and 4.1.0, and only matters in deployments that actually use input-value-based permission rules; no public exploit code has been identified at time of analysis.
Case-sensitivity bypass in Hugo's security.http.urls IP-literal deny rule lets builds running v0.162.0 through v0.165.x fetch URLs that the rule was configured to block - a mixed-case scheme such as 'HTTP://localhost/...' evades the deny match, re-enabling SSRF through resources.GetRemote. The issue is unauthenticated (PR:N) but local (AV:L): it only matters when a Hugo build processes attacker-influenced input and the operator depends on the IP-literal deny rule as the SSRF control, and it cannot be triggered against an already-served static site. No public exploit code has been identified and there is no confirmation of active exploitation, but a vendor patch is available in Hugo v0.166.0.
Information disclosure in Grav CMS before 2.0.25 lets unauthenticated remote attackers read sensitive files - configuration secrets and account password hashes - when the site is served by Microsoft IIS using the bundled webserver-configs/web.config over a case-insensitive filesystem such as NTFS, simply by varying the case of a folder name or extension (for example GET /user/CONFIG/system.YAML) so that none of the case-sensitive URL Rewrite deny rules match. The practical blast radius is narrower than the raw path-bypass suggests: whether a bypassed file is actually returned depends on MIME registration, with .json served by default while .yaml/.yml return HTTP 404.3 on a stock IIS unless a YAML MIME mapping has been added; the equivalent gap in webserver-configs/lighttpd.conf is lower risk because lighttpd typically runs on case-sensitive filesystems, and deployments behind Apache (.htaccess), nginx, Caddy, or the PHP built-in server are not affected. No public exploit identified at time of analysis, and while the vendor-released patch is Grav 2.0.25, upgrading alone is insufficient because the .htaccess installer heal does not rewrite web.config or lighttpd.conf, so operators must manually re-copy the corrected sample files.
OpenClaw (npm package 'openclaw') before 2026.7.1 lets an actor who can steer a tool-enabled agent create a persistent cron job that runs attacker-chosen commands with the privileges of the OpenClaw process user. A mixed-case payload 'kind' value slips past the agent-facing shell-execution guard and later normalizes into a command job, targeting the model-facing cron tool only. The vendor scores this 8.7 (High) on CVSS 4.0 (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H) and the vendor-released patch is 2026.7.1; no public exploit identified at time of analysis.
Authorization bypass in OpenClaw's Matrix integration (@openclaw/matrix) allows an authenticated Matrix participant to inherit another account's authority when their user identifier collides after case/Unicode folding. Versions 2026.2.2 through 2026.8.0 lowercase the complete Matrix user ID - including the case-sensitive server-name portion and historical localparts - before deriving the OpenClaw authorization identity, so an attacker controlling a protocol-valid, fold-equivalent identifier (display-name matching is not required) can gain allowlist, owner-command, exec-approval, or plugin-approval rights configured for the privileged account. The vendor rates this CVSS 7.7 with high confidentiality, integrity, and availability impact; real-world risk is moderate and gated by the attacker needing a valid authenticated Matrix account plus a registrable colliding identifier, and no public exploit identified at time of analysis.