CVE Vulnerability Catalog

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and leave hostname verification disabled, causing arbitrary server certificates, including self-signed certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. The fix changes the production TLS helpers to use the JVM default trust store and enables hostname verification, while retaining an explicitly named development-only no-verification helper. This issue is fixed in version 5.33.0.

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.31.0, inbound AMQP command assembly in src/main/java/com/rabbitmq/client/impl/CommandAssembler.java processes a content-bearing method and header whose remainingBodyBytes value is smaller than a following AMQP.FRAME_BODY payload. CommandAssembler.consumeBodyFrame subtracts the peer-controlled payload length before validating that it fits, drives remainingBodyBytes negative, and throws a raw UnsupportedOperationException instead of MalformedFrameException. A malicious or compromised broker peer can send this malformed sequence on an open nonzero channel to terminate frame processing and close the client connection, causing denial of service for work using that connection. This issue is fixed in version 5.31.0.

authentik is an open-source identity provider. Prior to 2026.2.6 and 2026.5.5, a diagnostic action on the LDAP Source API does not enforce the object-level read-authorization filter used by the rest of the API. Any party able to reach the API, including an unauthenticated client, can invoke the diagnostic action against a configured LDAP Source. The server then connects to the upstream directory using the source's configured bind credentials and returns a bounded set of directory entries. The response exposes the distinguished names of those entries and the names of the attributes present on them, revealing directory structure, naming conventions, and the existence of specific accounts and groups, but not attribute values. Deployments without a configured LDAP Source are not affected. This issue is fixed in versions 2026.2.6 and 2026.5.5.

A reflected XSS vulnerability in reportico-web <= 8.1.0 allows remote attackers to execute arbitrary JavaScript in a user's browser by including a malicious payload in the loadTemplate parameter with execute_mode=PREPARE in run.php.

ePA 3.x Integration implements the authorization workflow and writes Medical Information Objects to Germany's electronic patient record. Prior to 1.3.0, ePA 3.x Integration does not neutralize CRLF characters in values used by app/vau/VAUProtokoll.py to construct VAU inner HTTP requests. The build_inner_header function interpolates the uri, host, accept_type, content_type, content_length, USER_AGENT, and insurant_id values into request lines and headers, including x-useragent and x-insurantid. An authenticated attacker who controls a value can inject additional headers into the inner request. Depending on ePA server handling, an injected x-insurantid header can expose another patient's records, and injected Authorization headers can bypass the intended authentication or authorization context. Session-derived USER_AGENT input can also poison requests across the session. This issue is fixed in version 1.3.0.

Adaguc-server before version 7.2.2 contains a vulnerability causing a crash with a memory-safety fault when parsing a GeoJSON document with a malformed coordinate. The parser indexes array values without validating the JSON node type or coordinate length, leading to an out-of-bounds read or NULL pointer dereference. The issue affects the Polygon, LineString, MultiLineString, and MultiPolygon geometry branches.

Saleor versions from 3.14.67 to 3.21.67, 3.22.63, and 3.23.22 have a broken authorization check in saleor/permission/utils.py that can incorrectly authorize unauthenticated GraphQL requests. This allows anonymous callers to use the channelUpdate() mutation to change channel order settings such as allowUnpaidOrders even when the response reports PermissionDenied. The same permission utility can expose hidden objects through pageType() and translation() queries, including attributes with visibleInStorefront set to false.

Cross-site scripting vulnerability in the user documentation field in Beta Systems Software AG ANOW! Automate v.3.3.1.90 allows a remote attacker to execute arbitrary code.

In the must-gather component of Red Hat Advanced Cluster Management for Kubernetes, the cluster Proxy object is dumped in raw form, bypassing the oc inspect redaction that would normally sanitize sensitive fields. This exposes proxy basic-auth credentials in the must-gather archive, potentially disclosing sensitive authentication information to anyone with access to the archive.

In the must-gather component of Red Hat Advanced Cluster Management for Kubernetes, certain ACM wrapper Custom Resources that embed Secret data are collected without redaction. When an administrator runs must-gather, credentials and tokens are captured in cleartext in the resulting archive, potentially exposing sensitive information to anyone with access to the archive.

Joomla! Core versions 4.0.0-5.4.7 and 6.0.0-6.1.2 have improper ACL checks for batch copy actions. An improper access check allows unauthorized users to perform copy batch operations on uneditable items.

Joomla! Core versions 4.0.0-5.4.7 and 6.0.0-6.1.2 have improper ACL checks for category webservice endpoints. An improper access check allows unauthorized users to create categories via webservices endpoints.

The mise tool, managing developer tool versions, before version 2026.7.1 records mise/bin/mise with user and group ID 1001, and the installation process does not normalize ownership, allowing a local user with those IDs to replace the installed executable, especially when MISE_INSTALL_PATH targets a shared location like /usr/local/bin.

Trivy, a security scanner, before version 0.72.0 uses plugin manifest metadata to construct paths under ~/.trivy/plugins without confining plugin names to that root, allowing an attacker who persuades a user to install or run a malicious plugin to write the manifest and plugin binary to arbitrary user-writable paths.

MyBB, free and open source forum software, before version 1.8.40 in the User CP Buddy/Ignore List component does not validate reciprocal buddy-list updates correctly. Deleting an entry from the acting user's list updates the target account's buddy list, but the reciprocal search uses the deleted target UID instead of the acting user's UID, and the unchecked array_search() return value can be used as an array key, potentially removing the target account's first stored buddy.

The registration component in MyBB does not validate the text-based Security Question CAPTCHA correctly, allowing attackers to bypass the challenge via a specially crafted value. The question_id field is accepted without verifying if the identifier is valid, and if it is blank, forged, or expired, the request continues without a question-related error.

MyBB before version 1.8.40 does not consistently enforce single-use semantics for the built-in CAPTCHA, allowing remote attackers to bypass CAPTCHA controls through challenge replay. The successful validation paths in contact.php, member.php?action=do_resendactivation, member.php?action=do_lostpw, member.php?action=do_emailuser, and sendthread.php?action=do_sendtofriend do not call captcha::invalidate_captcha() for the default CAPTCHA.

MyBB before version 1.8.40 in the Admin CP Recovery Codes module does not validate requests correctly, allowing same-site attackers to rotate a victim administrator's recovery codes with a specially crafted URL. The action=recovery_codes page regenerates Two-Factor Authentication recovery codes on GET requests without request forgery protection.

MyBB before version 1.8.40 in the Email User controller does not sanitize sender names correctly, resulting in mail header injection. The fromname parameter is accepted without sanitization, and when mail_handler is set to the default PHP mail value, the sender name is used in Return-Path and Reply-To headers, allowing arbitrary headers to be injected with CRLF sequences.

MyBB before version 1.8.40 in the Mod CP Report Center does not check permissions consistently, allowing moderators without report-management permission to mark reports as resolved. The Mark Selected as Read handler is reachable with canmodcp even without canmanagereportedcontent or canmanagereportedposts, and when no forums are in scope, the UPDATE query executes without the expected permission-based limitation.