CVE-2026-133064 is a stored cross-site scripting (XSS) vulnerability in Moodle's SCORM objectives report. An authenticated user with content upload permissions can inject malicious scripts via insufficient sanitization of objective identifiers. When other users view the report, the malicious script executes in their browser, potentially exposing sensitive information or enabling unauthorized actions. The vulnerability affects multiple Moodle versions prior to fixed releases. A fix is available in Moodle versions 4.5.16, 5.1.0, 5.1.9, 5.2.5, and 5.3.1.
CVE-2026-133062 is a SQL injection vulnerability in Moodle's external database enrolment plugin. This flaw allows an authenticated user with course editing permissions to inject SQL commands due to insufficient sanitization of data passed to external database queries. Exploitation can lead to unauthorized viewing, modification, or deletion of sensitive records in the connected external database. The vulnerability affects multiple Moodle versions prior to fixed releases. A fix is available in Moodle versions 4.5.16, 5.1.0, 5.1.9, 5.2.5, and 5.3.1.
CVE-2026-133060 is a vulnerability in Moodle's Blackboard question import format where insufficient validation of file paths allows an authenticated user with import permissions to read arbitrary files accessible to the web server. This can lead to unauthorized disclosure of sensitive information. The issue affects multiple Moodle versions prior to fixed releases. A fix is available in Moodle versions 4.5.16, 5.1.0, 5.1.9, 5.2.5, and 5.3.1.
CVE-2026-133059 is a vulnerability in Moodle's grade feedback web service where group and course enrolment permissions are not properly verified. This flaw allows an authenticated user with non-editing teacher privileges to access grade feedback and user profile information from groups or courses they are not authorized to view, resulting in unauthorized information disclosure. The issue affects multiple Moodle versions prior to fixed releases. The vulnerability has a medium severity rating with a CVSS score of 4.3. Red Hat has assessed that this vulnerability does not affect any currently supported Red Hat products.
Eclipse Ditto versions 1.1.0 through 3.9.8 contain an authentication bypass vulnerability when pre-authentication is enabled. The gateway service improperly accepts a pre-authenticated subject from an undocumented URL query parameter, allowing unauthenticated attackers to impersonate any policy subject. This occurs because the gateway trusts the query parameter in addition to the HTTP header, and the default Helm chart configuration enables this insecure behavior. Attackers can read and modify Things and Policies with the permissions of the spoofed subject.
A use-after-free vulnerability was identified and fixed in the Linux kernel's SUNRPC subsystem, specifically in the write_gssp() function. The issue arises from improper reference counting of network namespaces when writing to /proc/net/rpc/use-gss-proxy, leading to a use-after-free condition. This flaw can cause kernel memory corruption due to accessing freed network namespace structures. The vulnerability affects Linux kernel version 3.10 and was addressed by ensuring proper reference counting and rejecting writes when the namespace is no longer valid.
PHP-FPM request smuggling through an unread HTTP request body.
PHP does not discard the unread part of an HTTP request body at request shutdown when the application has opened php://input without reading it to the end. When the front end reuses backend connections, which is not the default in nginx or Apache (for example nginx with fastcgi_keep_conn on, or Apache mod_proxy_fcgi with enablereuse=on), PHP-FPM can parse the leftover bytes as a new FastCGI request. An unauthenticated remote attacker can use a single crafted multipart/form-data request to forge a backend request with chosen parameters such as SCRIPT_FILENAME, REMOTE_ADDR and PHP_ADMIN_VALUE, which can lead to execution of attacker-controlled PHP code. With LSAPI, subsequent requests on the connection can be disrupted.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
SOAP information disclosure through malformed array dimensions.
The SOAP extension reads an uninitialized array position when decoding an encoded array whose arraySize attribute is empty, whitespace-only or non-numeric, or when such dimensions come from a WSDL definition. Four bytes of unrelated heap data can then be used as an integer key in the decoded array. An unauthenticated remote client can trigger this with a crafted request to a SoapServer endpoint, and a malicious SOAP server with a response to SoapClient. Heap memory is disclosed only if the application returns or otherwise exposes the decoded array.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Denial of service through folded HTTP response headers.
The HTTP stream wrapper joins each continuation line of a folded response header to the accumulated value by allocating a new string and copying the whole value, so a response with many short continuation lines takes disproportionate CPU time to parse. An attacker who controls an HTTP or HTTPS response fetched through file_get_contents(), fopen() or other stream functions, by making the application request a chosen URL or by influencing a server it already contacts, can keep PHP workers busy. Repeated or concurrent requests can cause a denial of service.
This issue affects PHP versions from 8.2.28 before 8.2.36, from 8.3.18 before 8.3.37, from 8.4.5 before 8.4.28 and 8.5.* before 8.5.13.
PHP-FPM epoll use-after-free can lead to local privilege escalation.
When catch_workers_output is enabled and the epoll event backend is used, the PHP-FPM master can close a worker's output pipe in fpm_child_close() without removing the associated event, and the delayed cleanup can free the worker record while its epoll registration is still active. A later event is then dispatched through a pointer into freed memory. A local attacker who can execute PHP code in an FPM worker can crash the master or execute code with its privileges, commonly root. catch_workers_output is disabled by default but enabled in the official PHP-FPM Docker images.
This issue affects PHP versions from 8.2.7 before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Timezone cache use-after-free can lead to remote code execution.
In non-thread-safe builds, a diagnostic written to a file-based error_log during module startup, for example for an invalid date.timezone value or a session configuration warning, causes the timezone cache to be allocated in startup memory that is freed while a reference to it is kept. A diagnostic raised early in the first request of a worker, such as the max_input_vars warning, then accesses the freed cache. On such a deployment an unauthenticated remote attacker can crash PHP-FPM, Apache mod_php or CGI workers with a crafted request. Arbitrary code execution may be possible and has been demonstrated with known memory addresses.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
A vulnerability in the Linux kernel s390 architecture probes code was fixed by correcting the opcode comparison for the cgrb instruction. The probes code incorrectly compared the last byte of the cgrb instruction against 0xe6 instead of the correct 0xe4. This issue affects Linux kernel version 3.12.
Use-after-free after interrupted session shutdown.
The session extension records the filename of the executing script when a session starts. If a fatal error occurs in an application callback while the session variables are destroyed at shutdown, such as stream_close() of a user-defined stream wrapper, the pointer is retained after the request memory is freed, and a later request handled by the same worker can free the stale string. An attacker who can trigger such a failing cleanup may crash the worker or corrupt memory; code execution has not been demonstrated. This requires the filename to be allocated in request memory, for example when the script is not cached by OPcache.
This issue affects PHP versions 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
A vulnerability in the Linux kernel s390 vmcp subsystem could leak kernel stack data to users with CAP_SYS_ADMIN privileges due to uninitialized session information. This issue has been fixed in Linux kernel versions 6.12.118, 6.18.64, and 7.3.2.
Partially overwritten session files can lead to remote code execution.
The files session save handler, which is the default, writes updated session data into the existing session file without first clearing it. If a write is interrupted, the file can contain the beginning of the new session followed by the end of the old one, and bytes of an ordinary string can later be unserialized as objects. An attacker who can influence the session data, for example through session upload progress, and interrupt a write at a suitable point may inject objects, which can lead to code execution when the application contains a suitable gadget chain. Session data can also be corrupted.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Mixed-case HTTPS and FTPS URLs can expose data in plaintext.
The HTTP and FTP stream wrappers recognise URL schemes case-insensitively, but enable TLS only when the scheme contains a lowercase "s" at a fixed position. A URL such as HTTPS:// or FTPS:// passed to file_get_contents(), fopen() or other stream functions, or received as an HTTP redirect target, is therefore handled over unencrypted HTTP or FTP. An attacker able to observe the network traffic can read data the application expected TLS to protect, including credentials, request bodies and transferred files.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
PHAR OpenSSL signature bypass via algorithm downgrade.
The Phar extension selects the signature verification method from the signature type stored in the archive, and only the OpenSSL types consult the separate .pubkey file holding the trusted public key. An attacker who can modify an OpenSSL-signed Phar archive, but not its public key file, can switch the signature type to a keyless hash such as SHA-256 with a recomputed digest, so the altered archive passes verification even with phar.require_hash enabled. An application that loads the archive may then execute attacker-controlled PHP code. Native, tar-based and zip-based phars are affected.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
Session serializer mismatch can lead to remote code execution.
Session upload progress, when enabled, can store attacker-controlled data in a session key using the php_binary or php_serialize session serializer. If the same session is later read with the php serializer, because session.serialize_handler is changed at runtime or differs between applications sharing a session store, bytes inside the key can be passed to the unserializer. A remote attacker able to submit a multipart upload can inject objects, which may lead to code execution when the reading application contains a suitable gadget chain, or to session corruption or denial of service.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
PHP-CGI out-of-bounds read and write during PATH_INFO correction.
The PHP CGI binary (php-cgi), in CGI and FastCGI mode with cgi.fix_pathinfo enabled (the default), can perform an out-of-bounds read and write when the path removed from SCRIPT_FILENAME or PATH_TRANSLATED is longer than the supplied PATH_INFO, or when PATH_INFO is empty. This requires a web server mapping that passes such inconsistent values, or a FastCGI listener reachable by untrusted clients. An unauthenticated remote attacker can crash the process, may obtain process memory if the application exposes PATH_INFO or PATH_TRANSLATED, and may corrupt memory. PHP-FPM and the Apache module are not affected.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.
SOAP use-after-free when processing DTD entity references.
The SOAP extension frees the document type definition (DTD) of a parsed XML document while attribute values can still refer to entities it owns, and can then read freed memory. Removing the DTD also bypasses the SOAP server's rejection of documents that contain one. An unauthenticated remote attacker who can send a crafted request to a SOAP endpoint, or who controls a WSDL or schema document loaded by the application, can crash the PHP process and cause denial of service. Memory disclosure and code execution have not been confirmed.
This issue affects PHP versions 8.2.* before 8.2.36, 8.3.* before 8.3.37, 8.4.* before 8.4.28 and 8.5.* before 8.5.13.