Monthly
Wails v2's BindingsAllowedOrigins wildcard matching can be bypassed when an application is configured with a trailing or partial-label wildcard such as https://myapp.com*, allowing an attacker-controlled origin sharing that literal prefix, for example myapp.community or myapp.com.attacker.com, to invoke bound Go methods once that origin is loaded in the webview. The documented subdomain-prefix pattern https://*.myapp.com and default configurations without such a wildcard are not affected, and realized impact depends on which Go methods the application exposes. The vendor rates this 7.6 HIGH under CVSS 4.0; no public exploit identified at time of analysis and no CISA KEV listing, and exploitation requires the non-default misconfiguration plus user/webview interaction to load the attacker origin.
Cache poisoning of raw repository file responses in GitLab CE/EE (all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2) lets a low-privileged authenticated user supply crafted repository references so that cached raw-file content is served to other users. When a targeted victim's CI/CD pipeline subsequently fetches that poisoned raw file, the pipeline executes attacker-controlled content, potentially exposing protected environment variables. Publicly available exploit code exists (referenced via a HackerOne report), but the issue is not confirmed as actively exploited (no CISA KEV listing); exploitation is rated high complexity (AC:H), requires authentication (PR:L), and success depends on a victim pipeline actually pulling and running the poisoned content, making this a credible, high-priority issue rather than an emergency.
Authentication bypass in Tegalog (Fumy Otegaru Memo Logger) by Nishishi Factory permits remote unauthenticated attackers to access the management console by exploiting a permissive regular expression (CWE-625) used during login validation. Once inside the console, an attacker can perform any operation the management interface exposes - including creating, modifying, or deleting memo log entries. No public exploit code has been identified at time of analysis, and the product is absent from CISA's Known Exploited Vulnerabilities catalog.
Rack::Sendfile in versions prior to 2.2.23, 3.1.21, and 3.2.6 allows remote attackers to inject regex metacharacters into X-Accel-Mapping request headers, enabling unescaped interpolation that manipulates the X-Accel-Redirect response header and causes nginx to serve unintended files from internal locations. No public exploit code or active exploitation has been confirmed; patch versions are available from the vendor.
Execution allowlist bypass in OpenClaw (versions prior to 2026.3.11) enables unauthenticated remote attackers to execute arbitrary commands by exploiting improper pattern normalization in matchesExecAllowlistPattern. The vulnerability stems from lowercasing and overly permissive glob matching logic that incorrectly allows the ? wildcard to match across POSIX path segments, circumventing intended security restrictions. No public exploit identified at time of analysis, though CVSS 8.8 severity reflects network-accessible attack vector with no authentication required and high integrity/availability impact.
CallBackery versions before 0.62.0 for Perl accept unintended values in form fields checked by createRxValidator. createRxValidator() is documented to anchor the supplied pattern at both ends, but builds /^${rx}$/ without grouping the pattern. An alternation such as yes|no then accepts any value starting with yes or ending with no, and $ also accepts a value with one trailing newline. An authenticated user can submit values the pattern was meant to reject, which an application may then write into generated configuration files.
Server-side request forgery in the @astrojs/netlify adapter (5.2.0 through 8.2.3) lets unauthenticated remote attackers make the Netlify Image CDN fetch URLs whose host they control, by embedding an allowlisted origin inside the path or query string of a request to the public /.netlify/images endpoint. The impact is limited: Netlify egress protections restrict which internal or external targets are actually reachable and image-transformation handling prevents fetched response bodies from being returned to the attacker, so no confidentiality or integrity impact has been demonstrated and only low availability impact is assessed (CVSS 6.3 per the 4.0 vector; independent assessment CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). No public exploit code has been identified at time of analysis, and the flaw is fixed in @astrojs/netlify 8.2.4.
External control of critical state data in Dell Secure Connect Gateway (SCG) 5.0 exposes sensitive information to remote unauthenticated attackers via network-accessible state manipulation. Affected are SCG 5.0 Appliance versions prior to 5.36.00.16 and SCG 5.0 Application versions prior to 5.36.00.00. Impact is limited to partial confidentiality loss (C:L) with no integrity or availability degradation, per CVSS; no public exploit code has been identified and this vulnerability is not listed in CISA KEV.
Tenant hijacking and request degradation in AshPhoenix (ash_phoenix 2.1.26 through 2.3.24) allows unauthenticated remote clients to force an Ash multi-tenant application to resolve an arbitrary tenant by supplying a crafted HTTP Host header. The root cause is that AshPhoenix.Helpers.get_subdomain/2 interpolated the configured root domain verbatim into a regex pattern, causing domain dots to act as any-character wildcards and the match to be applied unanchored and globally - so Host: foo.exampleXcom.attacker.net satisfied a rule intended to match only subdomains of example.com, returning foo as the tenant. A separate case-sensitivity flaw allowed TENANT.EXAMPLE.COM to bypass the allowlist check entirely. No CISA KEV listing and no public proof-of-concept have been identified at time of analysis, but exploitation requires no authentication and no special tooling.
Privilege escalation in Red Hat Advanced Cluster Security 4 (StackRox Central) allows authenticated OIDC token holders to gain unauthorized role assignments through unanchored regular expression matching in the Machine-to-Machine token exchange subsystem. When administrators configure M2M role mappings, RHACS matches incoming OIDC claim values against configured patterns without regex anchors, meaning an attacker whose claim value is a superstring of a mapped pattern - for example, 'superadmin' matching a pattern intended only for 'admin' - receives elevated roles unintentionally. No public exploit code or active exploitation has been identified at this time; the CVSS AC:H rating reflects a genuine complexity barrier requiring attacker knowledge of the target's role mapping configuration.
Wails v2's BindingsAllowedOrigins wildcard matching can be bypassed when an application is configured with a trailing or partial-label wildcard such as https://myapp.com*, allowing an attacker-controlled origin sharing that literal prefix, for example myapp.community or myapp.com.attacker.com, to invoke bound Go methods once that origin is loaded in the webview. The documented subdomain-prefix pattern https://*.myapp.com and default configurations without such a wildcard are not affected, and realized impact depends on which Go methods the application exposes. The vendor rates this 7.6 HIGH under CVSS 4.0; no public exploit identified at time of analysis and no CISA KEV listing, and exploitation requires the non-default misconfiguration plus user/webview interaction to load the attacker origin.
Cache poisoning of raw repository file responses in GitLab CE/EE (all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2) lets a low-privileged authenticated user supply crafted repository references so that cached raw-file content is served to other users. When a targeted victim's CI/CD pipeline subsequently fetches that poisoned raw file, the pipeline executes attacker-controlled content, potentially exposing protected environment variables. Publicly available exploit code exists (referenced via a HackerOne report), but the issue is not confirmed as actively exploited (no CISA KEV listing); exploitation is rated high complexity (AC:H), requires authentication (PR:L), and success depends on a victim pipeline actually pulling and running the poisoned content, making this a credible, high-priority issue rather than an emergency.
Authentication bypass in Tegalog (Fumy Otegaru Memo Logger) by Nishishi Factory permits remote unauthenticated attackers to access the management console by exploiting a permissive regular expression (CWE-625) used during login validation. Once inside the console, an attacker can perform any operation the management interface exposes - including creating, modifying, or deleting memo log entries. No public exploit code has been identified at time of analysis, and the product is absent from CISA's Known Exploited Vulnerabilities catalog.
Rack::Sendfile in versions prior to 2.2.23, 3.1.21, and 3.2.6 allows remote attackers to inject regex metacharacters into X-Accel-Mapping request headers, enabling unescaped interpolation that manipulates the X-Accel-Redirect response header and causes nginx to serve unintended files from internal locations. No public exploit code or active exploitation has been confirmed; patch versions are available from the vendor.
Execution allowlist bypass in OpenClaw (versions prior to 2026.3.11) enables unauthenticated remote attackers to execute arbitrary commands by exploiting improper pattern normalization in matchesExecAllowlistPattern. The vulnerability stems from lowercasing and overly permissive glob matching logic that incorrectly allows the ? wildcard to match across POSIX path segments, circumventing intended security restrictions. No public exploit identified at time of analysis, though CVSS 8.8 severity reflects network-accessible attack vector with no authentication required and high integrity/availability impact.
CallBackery versions before 0.62.0 for Perl accept unintended values in form fields checked by createRxValidator. createRxValidator() is documented to anchor the supplied pattern at both ends, but builds /^${rx}$/ without grouping the pattern. An alternation such as yes|no then accepts any value starting with yes or ending with no, and $ also accepts a value with one trailing newline. An authenticated user can submit values the pattern was meant to reject, which an application may then write into generated configuration files.
Server-side request forgery in the @astrojs/netlify adapter (5.2.0 through 8.2.3) lets unauthenticated remote attackers make the Netlify Image CDN fetch URLs whose host they control, by embedding an allowlisted origin inside the path or query string of a request to the public /.netlify/images endpoint. The impact is limited: Netlify egress protections restrict which internal or external targets are actually reachable and image-transformation handling prevents fetched response bodies from being returned to the attacker, so no confidentiality or integrity impact has been demonstrated and only low availability impact is assessed (CVSS 6.3 per the 4.0 vector; independent assessment CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L). No public exploit code has been identified at time of analysis, and the flaw is fixed in @astrojs/netlify 8.2.4.
External control of critical state data in Dell Secure Connect Gateway (SCG) 5.0 exposes sensitive information to remote unauthenticated attackers via network-accessible state manipulation. Affected are SCG 5.0 Appliance versions prior to 5.36.00.16 and SCG 5.0 Application versions prior to 5.36.00.00. Impact is limited to partial confidentiality loss (C:L) with no integrity or availability degradation, per CVSS; no public exploit code has been identified and this vulnerability is not listed in CISA KEV.
Tenant hijacking and request degradation in AshPhoenix (ash_phoenix 2.1.26 through 2.3.24) allows unauthenticated remote clients to force an Ash multi-tenant application to resolve an arbitrary tenant by supplying a crafted HTTP Host header. The root cause is that AshPhoenix.Helpers.get_subdomain/2 interpolated the configured root domain verbatim into a regex pattern, causing domain dots to act as any-character wildcards and the match to be applied unanchored and globally - so Host: foo.exampleXcom.attacker.net satisfied a rule intended to match only subdomains of example.com, returning foo as the tenant. A separate case-sensitivity flaw allowed TENANT.EXAMPLE.COM to bypass the allowlist check entirely. No CISA KEV listing and no public proof-of-concept have been identified at time of analysis, but exploitation requires no authentication and no special tooling.
Privilege escalation in Red Hat Advanced Cluster Security 4 (StackRox Central) allows authenticated OIDC token holders to gain unauthorized role assignments through unanchored regular expression matching in the Machine-to-Machine token exchange subsystem. When administrators configure M2M role mappings, RHACS matches incoming OIDC claim values against configured patterns without regex anchors, meaning an attacker whose claim value is a superstring of a mapped pattern - for example, 'superadmin' matching a pattern intended only for 'admin' - receives elevated roles unintentionally. No public exploit code or active exploitation has been identified at this time; the CVSS AC:H rating reflects a genuine complexity barrier requiring attacker knowledge of the target's role mapping configuration.