Monthly
Client-side field-level encryption (CSFLE) in the MongoDB C# / .NET Driver before 3.13.0 can silently fail to encrypt fields that an application designated for protection, so data intended to be ciphertext is stored and returned in cleartext. The flaw sits in the schema-construction component that turns caller-supplied field identifiers into pattern expressions, so it only affects applications that build automatic-encryption schemas through the affected PatternProperty overload; the same defect can also make a rule apply more broadly than intended. Discovery requires no user interaction, and the party reading the unprotected values only needs ordinary authenticated read access to the stored data (PR:L in the assessed vector) - not the encryption keys - though it is not a default configuration and no public exploit was identified at time of analysis; the driver fixes it in 3.13.0.
Credential header leakage in follow-redirects 1.16.0 allows remote attackers to receive sensitive headers that should have been stripped when a request follows a cross-origin or HTTPS-to-HTTP redirect to an attacker-controlled target. The flaw only manifests when an application explicitly declares a sensitive header whose name contains the regular-expression metacharacters ^ or |, so conventionally named headers and default configurations are not affected. The vendor fixed the issue in 1.16.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated remote command execution is possible in MLJAR Mercury 3.0.0 through 3.2.3 because a missing comma in the BLOCKED_PATTERNS list merges the /lab and /api/terminals regular expressions into a single pattern, so requests to /api/terminals no longer match the anonymous-endpoint blocklist and are proxied straight to Jupyter Server's terminal API. An attacker with network access to a Mercury instance that serves dashboards to anonymous users can therefore open an interactive operating-system shell and run commands with the privileges of the Mercury process (CVSS 10.0, AV:N/AC:L/PR:N/UI:N/S:C). All severity signals agree - network reachability with no credentials or user interaction, scope change into the underlying Jupyter Server, and high confidentiality/integrity/availability impact - and the only limiting factor is that the instance must be reachable and running an affected version; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authorization bypass in HashiCorp Consul's Connect service mesh allows a low-privileged authenticated service to communicate with destination services it is not authorized to reach. The flaw originates in Consul's Envoy RBAC rule generation: unescaped special characters in service names, namespaces, or partitions cause the generated matching rules to be overly permissive, defeating the Connect intentions authorization model. No public exploit or CISA KEV listing exists at time of analysis; fixes are available across Consul open-source and Enterprise release trains.
Account takeover in GitHub Enterprise Server (all versions prior to 3.21) is possible through an OAuth redirect URI validation bypass caused by a flawed regular expression (CWE-185). An attacker who knows a first-party OAuth application's registered callback URL can craft a malicious authorization link that leaks the victim's OAuth authorization code to an attacker-controlled domain, granting access to the victim's account with the scopes of that application. Reported via the GitHub Bug Bounty program; there is no public exploit identified at time of analysis, EPSS is very low (0.05%), and CISA SSVC records exploitation status as none.
A regex-based bypass vulnerability in the @dicebear/converter npm package allows attackers to circumvent SVG dimension sanitization by injecting decoy <svg tags in XML constructs. Applications using @dicebear/converter on Node.js to process untrusted SVG input are vulnerable to denial of service through unbounded memory allocation when rendering malformed SVGs. The CVSS score of 7.5 reflects the high availability impact with network-accessible attack vector requiring no authentication or user interaction.
ReDoS in fast-xml-parser before fix via crafted XML. PoC and patch available.
Regex metacharacter injection in @astrojs/netlify prior to 8.1.2 causes the Netlify Image CDN allowlist to be broader than the developer intended, allowing optimization of images from unintended URL paths on already-allowed hostnames. The root cause is that remotePatternToRegex() escapes dots in hostnames but passes literal pathname values into the generated regex unescaped, so a pathname like /img/v1.0/file silently becomes a wildcard that matches /img/v1X0/file or /img/v1/0/file. No active exploitation has been confirmed (not in CISA KEV), though a working proof-of-concept is included in the GHSA advisory; CVSS 3.7 with AC:H reflects the constrained but network-accessible impact.
Sigstore attestation verification in GitHub CLI prior to 2.97.0 can be defeated when an attacker registers a lookalike repository whose name contains dot characters that function as regex wildcards - for example, github/artifact.attestations-workflows matching a matcher intended solely for github/artifact-attestations-workflows. The `gh attestation verify` command in pkg/cmd/attestation/verify/policy.go constructed Certificate Subject Alternative Name (SAN) matchers by interpolating `--signer-repo` and `--signer-workflow` flag values directly into regex patterns without calling regexp.QuoteMeta(), allowing any dot or other metacharacter in a GitHub-permitted name to act as a wildcard. No public exploit has been identified at time of analysis; the CVSS 4.0 AT:P designator confirms exploitation requires the attacker to first position a valid lookalike repository with legitimate Sigstore attestations, making this a targeted rather than opportunistic threat.
Unauthenticated remote file disclosure in Webmin (all versions prior to 2.641) exposes the contents of any .conf file residing within module directories. The root cause is a flawed regular expression (CWE-185) that was intended to restrict accessible file paths but can be bypassed with a crafted request, allowing unauthenticated network attackers to read configuration files that may contain credentials, API keys, or other sensitive deployment data. No public exploit or CISA KEV listing has been identified at time of analysis, though the zero-authentication, network-accessible attack surface makes this straightforward to probe at scale.
Client-side field-level encryption (CSFLE) in the MongoDB C# / .NET Driver before 3.13.0 can silently fail to encrypt fields that an application designated for protection, so data intended to be ciphertext is stored and returned in cleartext. The flaw sits in the schema-construction component that turns caller-supplied field identifiers into pattern expressions, so it only affects applications that build automatic-encryption schemas through the affected PatternProperty overload; the same defect can also make a rule apply more broadly than intended. Discovery requires no user interaction, and the party reading the unprotected values only needs ordinary authenticated read access to the stored data (PR:L in the assessed vector) - not the encryption keys - though it is not a default configuration and no public exploit was identified at time of analysis; the driver fixes it in 3.13.0.
Credential header leakage in follow-redirects 1.16.0 allows remote attackers to receive sensitive headers that should have been stripped when a request follows a cross-origin or HTTPS-to-HTTP redirect to an attacker-controlled target. The flaw only manifests when an application explicitly declares a sensitive header whose name contains the regular-expression metacharacters ^ or |, so conventionally named headers and default configurations are not affected. The vendor fixed the issue in 1.16.1; no public exploit code or confirmed active exploitation was identified at time of analysis.
Unauthenticated remote command execution is possible in MLJAR Mercury 3.0.0 through 3.2.3 because a missing comma in the BLOCKED_PATTERNS list merges the /lab and /api/terminals regular expressions into a single pattern, so requests to /api/terminals no longer match the anonymous-endpoint blocklist and are proxied straight to Jupyter Server's terminal API. An attacker with network access to a Mercury instance that serves dashboards to anonymous users can therefore open an interactive operating-system shell and run commands with the privileges of the Mercury process (CVSS 10.0, AV:N/AC:L/PR:N/UI:N/S:C). All severity signals agree - network reachability with no credentials or user interaction, scope change into the underlying Jupyter Server, and high confidentiality/integrity/availability impact - and the only limiting factor is that the instance must be reachable and running an affected version; no public exploit code or confirmed active exploitation was identified at time of analysis.
Authorization bypass in HashiCorp Consul's Connect service mesh allows a low-privileged authenticated service to communicate with destination services it is not authorized to reach. The flaw originates in Consul's Envoy RBAC rule generation: unescaped special characters in service names, namespaces, or partitions cause the generated matching rules to be overly permissive, defeating the Connect intentions authorization model. No public exploit or CISA KEV listing exists at time of analysis; fixes are available across Consul open-source and Enterprise release trains.
Account takeover in GitHub Enterprise Server (all versions prior to 3.21) is possible through an OAuth redirect URI validation bypass caused by a flawed regular expression (CWE-185). An attacker who knows a first-party OAuth application's registered callback URL can craft a malicious authorization link that leaks the victim's OAuth authorization code to an attacker-controlled domain, granting access to the victim's account with the scopes of that application. Reported via the GitHub Bug Bounty program; there is no public exploit identified at time of analysis, EPSS is very low (0.05%), and CISA SSVC records exploitation status as none.
A regex-based bypass vulnerability in the @dicebear/converter npm package allows attackers to circumvent SVG dimension sanitization by injecting decoy <svg tags in XML constructs. Applications using @dicebear/converter on Node.js to process untrusted SVG input are vulnerable to denial of service through unbounded memory allocation when rendering malformed SVGs. The CVSS score of 7.5 reflects the high availability impact with network-accessible attack vector requiring no authentication or user interaction.
ReDoS in fast-xml-parser before fix via crafted XML. PoC and patch available.
Regex metacharacter injection in @astrojs/netlify prior to 8.1.2 causes the Netlify Image CDN allowlist to be broader than the developer intended, allowing optimization of images from unintended URL paths on already-allowed hostnames. The root cause is that remotePatternToRegex() escapes dots in hostnames but passes literal pathname values into the generated regex unescaped, so a pathname like /img/v1.0/file silently becomes a wildcard that matches /img/v1X0/file or /img/v1/0/file. No active exploitation has been confirmed (not in CISA KEV), though a working proof-of-concept is included in the GHSA advisory; CVSS 3.7 with AC:H reflects the constrained but network-accessible impact.
Sigstore attestation verification in GitHub CLI prior to 2.97.0 can be defeated when an attacker registers a lookalike repository whose name contains dot characters that function as regex wildcards - for example, github/artifact.attestations-workflows matching a matcher intended solely for github/artifact-attestations-workflows. The `gh attestation verify` command in pkg/cmd/attestation/verify/policy.go constructed Certificate Subject Alternative Name (SAN) matchers by interpolating `--signer-repo` and `--signer-workflow` flag values directly into regex patterns without calling regexp.QuoteMeta(), allowing any dot or other metacharacter in a GitHub-permitted name to act as a wildcard. No public exploit has been identified at time of analysis; the CVSS 4.0 AT:P designator confirms exploitation requires the attacker to first position a valid lookalike repository with legitimate Sigstore attestations, making this a targeted rather than opportunistic threat.
Unauthenticated remote file disclosure in Webmin (all versions prior to 2.641) exposes the contents of any .conf file residing within module directories. The root cause is a flawed regular expression (CWE-185) that was intended to restrict accessible file paths but can be bypassed with a crafted request, allowing unauthenticated network attackers to read configuration files that may contain credentials, API keys, or other sensitive deployment data. No public exploit or CISA KEV listing has been identified at time of analysis, though the zero-authentication, network-accessible attack surface makes this straightforward to probe at scale.