Missing authorization in the Asgaros Forum WordPress plugin (versions through 3.4.0) lets a logged-in low-privilege account reach a forum function that should be gated by a capability check, resulting in limited information disclosure. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, score 4.3) confirms that an attacker must already hold an account on the target site - typically any registered forum member - because the flaw is a missing authorization check rather than an unauthenticated entry point, and the impact is confined to confidentiality with no integrity or availability effect. There is no CISA KEV listing and no public exploit code identified at time of analysis, so this is a moderate, low-priority issue; sites that do not allow untrusted user registration sharply reduce their exposure.
Cookie-parser confusion in OWASP Coraza WAF prior to 3.8.1 allows unauthenticated remote attackers to hide cookie-carried attack payloads from SecRules that inspect REQUEST_COOKIES or REQUEST_COOKIES_NAMES, because Coraza splits a Cookie header into name/value pairs differently than the protected backend application does. The bypass applies only when a Web Application Firewall ruleset is scoped to specific cookie names or values and the backend is a parser confirmed to trim boundary control characters - PHP's $_COOKIE and Python's http.cookies - while Node's cookie package and current Werkzeug 3.1.9 split the header the same way Coraza does, so exploitation does not apply there; the CVSS vector (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N, score 4.0) reflects that attacker-supplied data repositions the name/value boundary across a security-authority change, producing limited integrity impact with high attack complexity and no availability or confidentiality effect. There is no public exploit identified at time of analysis, and the issue is fixed in version 3.8.1; this is a modest-severity WAF-bypass condition rather than an emergency, but operators running cookie-scoped rules against PHP or Python backends should treat it as a real detection gap.
GET-side WAF rule bypass in OWASP Coraza WAF 3.0.0 through 3.7.x lets unauthenticated attackers evade signature matching when the library is deployed through non-net/http integrations such as coraza-spoa, coraza-proxy-wasm, or custom FFI/WASM hosts. When a URI containing a raw control byte (0x00-0x1F or 0x7F) makes Go's url.ParseRequestURI fail, Coraza's error branch leaves QUERY_STRING, ARGS_GET, ARGS_GET_NAMES, and the GET-derived portion of ARGS empty, so rules targeting those variables - the default target set for most OWASP CRS GET-side rules - never fire on the attacker-controlled query content, even though a downstream component may still parse and act on it. The bundled coraza/v3/http integration is unaffected because Go net/http rejects such malformed request targets with a 400 before Coraza is invoked, and exploitation additionally requires a backend that still consumes the dropped parameters, so this is a genuine but defense-in-depth-only bypass; no public exploit code was identified at time of analysis and CVSS is 4.0 (AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N). Fixed in 3.8.0.
Null pointer dereference in OpenPrinting CUPS allows unauthenticated remote attackers who can submit jobs to a shared printer queue to crash the cupsd print daemon, causing a temporary denial of service for all printing services. Exploitation requires a vulnerable version that still ships the deprecated embedded job-ticket comment feature and a single crafted PostScript or PDF file submitted via the Print-Job operation whose first lines contain a malformed %cupsJobTicket: entry. Impact is bounded to a brief daemon crash with automatic restart-there is no code execution or data exposure-and no public exploit code has been identified at time of analysis.
Ubuntu Linux is the vendor attribution for CVE-2026-105516, but no description, CVSS vector, CWE, CPE, or affected package detail accompanies the record, so the specific impact on any Ubuntu release cannot currently be stated. Exploitation status is unconfirmed: no public exploit identified at time of analysis and no CISA KEV listing was provided. Risk cannot be meaningfully assessed until the corresponding Ubuntu Security Notice and NVD entry are retrieved and mapped to concrete packages and releases.
CVE-2026-105517 is recorded against Ubuntu Linux, with the only attribution in the available intelligence being a vendor:ubuntu report; the record carries no description, no CVSS score or vector, no CWE mapping, no CPE strings, no EPSS estimate, and no CISA KEV entry. Because the affected component, version range, and attack surface are all unspecified, the concrete security impact cannot be determined from this data alone, and no public exploit code has been identified at time of analysis. Risk cannot be meaningfully assessed until the corresponding Ubuntu Security Notice is retrieved to identify the package, vulnerable versions, and any prerequisites such as authentication or non-default configuration.