CVE-2026-110682 is a vulnerability in Cpanel::JSON::XS Perl module versions 4.42 up to but not including 4.80. It involves an interpretation conflict in the incremental JSON parser (incr_parse) where input chunking can alter the decoded value of top-level numbers. Because allow_nonref is enabled by default, the parser decodes partial input chunks differently depending on read boundaries, allowing a peer controlling these boundaries to influence the number and content of decoded messages.
CVE-2026-100351 is an authentication bypass vulnerability in the kin-openapi library's openapi3filter.ValidationHandler.Middleware. It arises when a downstream gorilla/mux router uses UseEncodedPath(), causing a mismatch between the decoded path used for validation and the encoded path used for routing. This allows an unauthenticated request with an encoded path to bypass authentication and reach a protected handler. The issue affects kin-openapi versions from 0.144.0 up to but not including 0.147.0. The vulnerability can lead to unauthorized execution of protected handlers without invoking the authentication callback.
NGINX JavaScript (njs) contains a vulnerability in its XML module where entity-backed XML attributes are inconsistently exposed during canonicalization. This inconsistency can cause certain XML attributes to appear missing or truncated while signature verification still succeeds. This affects signed-XML consumers such as nginx-saml, potentially allowing replay attacks or acceptance of responses outside their intended context. The vulnerability does not allow signature or identity forgery and has no direct availability impact. It is a data plane issue without control plane exposure.
OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. Prior to 3.8.1, internal/cookies.ParseCookies in internal/cookies/cookies.go handles boundary ASCII control characters and control-only or empty cookie names differently from several backend cookie parsers. An unauthenticated attacker can craft a Cookie header so Coraza indexes or drops a cookie under a different name or value from the backend application, causing rules targeting REQUEST_COOKIES or REQUEST_COOKIES_NAMES to miss application-visible attacker data. Exploitation depends on the backend parser and affected rule scope, and interior control characters with inconsistent backend behavior are outside this advisory's remediation. This issue is fixed in version 3.8.1.
CVE-2026-107825 is an improper input validation vulnerability in Coraza WAF versions 3.0.0 through 3.7.x. The ProcessURI function fails to properly handle malformed URIs containing control bytes, causing query parameters to be omitted from internal variables while downstream integrations may still process them. This discrepancy allows unauthenticated attackers to bypass security rules targeting query parameters. The issue is fixed in version 3.8.0.
CVE-2026-106430 is a medium severity vulnerability in the MongoDB C++ Driver versions 3.0.0 up to but not including 4.6.1. The vulnerability arises because the driver discards content after an embedded NUL byte in certain field and collection names, leading to interpretation conflicts between the driver and the application. An authenticated user who can influence these names may cause the application to read or rename unintended fields or collections using the application's existing database credentials.
CVE-2026-73511 is an authentication bypass vulnerability in Envoy proxy caused by inconsistent path matching behavior with backend servers that strip semicolon matrix parameters per path segment. This allows a remote attacker to bypass path-based access controls by crafting requests that cause Envoy to select an unprotected fallback path while the backend resolves the protected resource. The issue affects Envoy versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 and is fixed in these versions.
Envoy proxy versions prior to 1.36.10, 1.37.6, 1.38.4, and 1.39.1 contain a vulnerability where inconsistent path canonicalization allows bypassing path-based authorization. When the ignore_path_parameters_in_path_matching option is enabled, the router strips semicolon suffixes before matching, but the RBAC url_path matcher evaluates the raw path. This discrepancy can let unauthenticated clients bypass DENY rules on protected routes. The issue is fixed in the specified versions.
CVE-2026-81378 is a high-severity vulnerability in Microsoft Visual Studio Code where an interpretation conflict allows an unauthorized attacker to bypass a security feature over a network. The issue affects versions from 1.0.0 up to but not including 1.136.2. An official fix is available in version 1.136.2.
CVE-2026-63435 is a medium severity vulnerability in the mikel mail Ruby package affecting versions prior to 2.9.1. It involves improper validation of syntactic correctness in email header decoding functions, allowing crafted malformed RFC 2047 encoded-words to cause address spoofing in From, To, or Reply-To headers. This can lead to spoofed sender or recipient addresses being displayed or authorized incorrectly.
A critical vulnerability in goauthentik authentik prior to versions 2026.2.6 and 2026.5.5 allows an attacker with an account on the source identity provider to perform account takeover. The flaw involves an XML comment injection in the NameID field when using non-default user-matching modes (USERNAME_LINK or EMAIL_LINK), causing truncation of the interpreted value and enabling binding of the attacker's identity to a victim's account without needing the victim's password or the identity provider's private key. This issue does not affect the default unique-identifier matching mode or authentik's outbound SAML Provider role. The vulnerability is fixed in versions 2026.2.6 and 2026.5.5.
CKAN MCP Server is a tool for querying CKAN open data portals. Prior to 0.4.112, canonicalizeParams in src/utils/cache.ts serializes request parameters with unescaped ampersand, equals-sign, and vertical-bar delimiters, allowing different logical parameter sets used by buildCacheKey to collide and an attacker to prime a shared cache with a response for a victim's distinct query. This issue is fixed in version 0.4.112.
CVE-2026-49473 affects the @cedar-policy/authorization-for-expressjs middleware versions prior to 0.3.0. The vulnerability arises from a mismatch in how the middleware and Express.js handle request URLs: the middleware uses req.originalUrl (including query strings) for authorization checks, while Express routes requests based only on the path component. This discrepancy allows an attacker to bypass stricter authorization policies by appending query strings to requests, causing the middleware to authorize less restrictive actions incorrectly. The issue is fixed in version 0.3.0.
IBM i 7.6, 7.5, 7.4, and 7.3 could allow a remote authenticated attacker to bypass security restrictions due to an interpretation conflict in the multipart parser.
Apache Airflow's Backfill API authorized a request against a Dag id supplied by the caller whenever the `backfill_id` path segment failed to parse. The authorization dependency parsed it with `int()` while the route handler parsed it as pydantic's `NonNegativeInt`, which accepts values `int()` rejects (`1.0` coerces to `1`); FastAPI resolves dependencies before endpoint validation, so the two acted on different Dags. An authenticated user holding edit permission on any single Dag could therefore read, pause and cancel backfills belonging to any other Dag, including moving another Dag's queued runs to `failed`. No non-default configuration is required and backfill ids are sequential, so finding a target is trivial. Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.
A flaw was found in openshift/oauth-proxy. The proxy sets authenticated identity headers using only dash-variant keys (X-Forwarded-User) but does not strip underscore-variant keys (X_Forwarded_User) from incoming requests. WSGI and PHP frameworks normalize both variants to the same variable, allowing an authenticated low-privilege user to smuggle a forged identity that may override the legitimate authenticated identity in the upstream application.
@hapi/content provided HTTP Content-* headers parsing. Prior to 6.0.2, Content.disposition() retained the last occurrence of each duplicate parameter while Content.type() retained the first occurrence of duplicate charset and boundary parameters, creating a parameter-smuggling primitive when another component in the request-processing chain resolves duplicates the opposite way. This can allow an upload filename allowlist bypass in headers such as Content-Disposition: form-data; name="file"; filename="safe.txt"; filename="shell.php". This issue is fixed in version 6.0.2.
Elysia v1.4.28 is vulnerable to denial-of-service attacks due to CPU exhaustion in the form data normalization code.
Elysia uses `getAll` to retrieve value from FormData. It is called directly relative to the total number of key-value pairs in the form data. The total amount of work the for loop has to do grows quadratically, so doubling the number of unique key-value pairs quadruples the amount of work. In the above PoC, each .getAll call scans through all of the `n` key-value pairs in the form data. Because there are `n` unique keys in the form data, there are .getAll calls, so in total the form data normalizer has to scan `n` x `n` key-value pairs.
### Impact
Endpoints using `multipart/form-data`
### Patches
1.4.29
### Workarounds
no 100% confirm workaround beside updating the patch
A vulnerability in guzzlehttp/psr7 prior to version 2.12.3 allows the Uri::assertValidHost() function to accept URI host components with authority delimiters, embedded ports, or malformed IPv6 brackets. This causes Uri::getHost() to produce a different host value than the URI authority used in security or routing decisions. The issue is fixed in version 2.12.3.