CVE-2026-113812 is a critical vulnerability in Mozilla::CA versions before 20261020 for Perl. The CA certificate bundle includes the "emSign ECC Root CA - G3" root, which trusts intermediate certificates with publicly compromised private keys. This flaw allows an attacker who can intercept or redirect client traffic to impersonate TLS servers. Clients using IO::Socket::SSL may fall back to this vulnerable CA bundle depending on configuration. Users should verify their CA store and apply vendor updates if relying on the system store.
## Review scope and evidence limits
Package: @apostrophecms/import-export, version 3.7.0.
Release tag reviewed: @apostrophecms/import-export@3.7.0, commit 9500b8b0e1d630d5e07fbb5fd2c25ed0943845ce (September 30, 2026).
Current main reviewed: 5ce3732be0ebdebb4db0f8ef160c81e8671157e6.
The importer, gzip extractor, import permission gate, and core permission implementation have no differences between that release tag and the reviewed main. This follow-up is a static remediation review. We have not repeated the original end-to-end reproductions against the latest release or tested a deployed site. Current exploitability and impact therefore still require maintainer validation; the observations below establish that the reported security checks remain absent in public source. The original emailed PDF contains the original reproduction material. Please refer to that existing private attachment.
## Archive duplicate continuation permits unauthorized published-content replacement
The overrideDuplicates() continuation still accepts client-supplied replacement choices, rather than binding them to a server-maintained, user-owned duplicate analysis. The replacement and write helpers do not establish a single canonical resource identity and authorization context before the update. This leaves the reported gap between draft editing authority and the published target selected for replacement unresolved at source level.
The original report describes a contributor crossing the publication boundary through duplicate replacement on an import-enabled localized type. We have not repeated that end-to-end sequence on 3.7.0.
Suggested remediation: bind continuation state to the initiating user, archive, job, permitted source/target mapping, locale and mode; reject inconsistent identity metadata; derive permissions from the actual loaded target and require publication authority for published targets.
Source: overrideDuplicates(), replaceDocId(), and insertOrUpdateDoc() in the [importer](https://github.com/apostrophecms/apostrophe/blob/5ce3732be0ebdebb4db0f8ef160c81e8671157e6/packages/import-export/lib/methods/import.js).
## Coordination
Vivek R / Winfunc
Original reporting team: Mufeed VH / Winfunc
CVE-2026-111755 is a high-severity vulnerability in the node-follow-redirects library, a Node.js HTTP and HTTPS client wrapper. It affects specific versions 1.2.4-1, 1.13.1-1, and 1.14.5-1. The vulnerability has a CVSS 4.0 base score of 8.2, indicating a network attack vector with low complexity and no user interaction required. The vulnerability allows partial impact on confidentiality but no impact on integrity or availability. No public exploits or known active exploitation have been reported.
Bulletin ID: 2026-058-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 07/16/2026 10:15 AM PDT Description: Bedrock AgentCore Python SDK (bedrock-agentcore) is an open-source Python library that provides client tools for building AI agents on the Amazon Bedrock AgentCore platform. We identified CVE-2026-15737 in the OpenTelemetry instrumentation of the SDK. Affected versions wrote raw user prompts and complete agent responses into OpenTelemetry span attributes on every invocation without filtering or masking. These spans flow into the customer's aws/spans CloudWatch log group, where a local authenticated user with CloudWatch Logs read access could access the potentially sensitive content. Impacted versions: 1.4.8, 1.5.0 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
CVE-2026-111750 is a medium severity vulnerability in the Python aiohttp asynchronous HTTP client/server framework. It affects multiple specific versions of python-aiohttp. The vulnerability has a CVSS 4.0 base score of 6.3, indicating a network attack vector with low attack complexity and no user interaction required, but partial impacts on confidentiality, integrity, and availability. No public exploits or known active exploitation are reported. No patch or remediation information is provided in the available data.
CVE-2026-111065 is a medium severity vulnerability in python-aiohttp, an asynchronous HTTP client/server framework for asyncio. The vulnerability has a CVSS 4.0 base score of 6.9, indicating a network exploitable issue with low attack complexity and no privileges or user interaction required. The impact is limited to a low severity impact on availability with no confidentiality or integrity impact. Multiple specific versions of python-aiohttp are affected.
CVE-2026-111063 is a medium severity vulnerability affecting multiple specific versions of the Python aiohttp asynchronous HTTP client/server framework. The vulnerability has a CVSS 4.0 base score of 6.3, indicating a network exploitable issue with low complexity and no user interaction required. There is no information about active exploitation or available patches in the provided data.
SGLang through 0.5.22 contains a denial of service vulnerability that allows API clients to abort other users' in-flight generation requests by supplying a short client-controlled rid. Attackers can submit streaming /generate requests with single hex character rids and disconnect, triggering prefix-matching abort logic that terminates all other clients' requests.
Microsoft fixed a bug in the classic Outlook desktop client for Windows that caused the Copilot Chat and Copilot buttons to be missing for some users. The issue was due to Outlook failing to retrieve certain account information from the user's profile. The missing buttons affected users with valid Copilot licenses, preventing access to Copilot features in classic Outlook, though Copilot remained accessible via Outlook on the web and the standalone Copilot app. Microsoft provided a workaround involving enabling the "Show Apps in Outlook" setting and recommended using the new Outlook client or creating a new profile if the issue persisted. The bug was resolved with an update after resurfacing following recent changes.
Generation of Error Message Containing Sensitive Information vulnerability in Apache Camel gRPC component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When a route behind a gRPC consumer failed, the exception's message was placed into the gRPC status description. Unlike the status cause, which stays local to the server, the description is transmitted to the calling client, so an external caller able to provoke a failure could read the internal error message. What that discloses depends on the exception, and in practice includes class and package names, paths, host names and connection detail carried in messages. This is the gRPC member of the same unmuted-consumer-exception family as the knative, mina and CXF advisories published alongside it.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. A muteException consumer option, defaulting to true, puts a generic description in the status instead of the route exception's message. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, map failures onto an explicit status in an onException handler so the framework never copies the exception message into the description.
Improper Certificate Validation vulnerability in Apache Camel Knative component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1.
When SSL was enabled on the Knative HTTP client but no truststore was configured, the client options fell back to trusting every presented certificate rather than to the JVM's default trust anchors. A deployment that switched TLS on without also configuring a truststore therefore obtained an encrypted connection with no peer authentication, which an attacker positioned on the network path can terminate and read. The dangerous state is reached by omission rather than by an explicit opt-in, which is what makes it a framework defect: turning TLS on should not be the thing that turns certificate validation off.
Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. With no truststore configured the trust options are now left unset so the JVM default trust anchors apply, the same fallback SSLContextParameters and the rest of Camel use. Trusting every certificate is now reached only by asking for it explicitly through the trust.all property, which remains available for development against a cluster with a self-signed certificate. For deployments that cannot upgrade immediately, configure a truststore explicitly wherever SSL is enabled. After upgrading, a deployment that was relying on the implicit trust-all behaviour must either configure a truststore or set the trust.all property deliberately.
The Tourfic – AI Powered Travel Booking, Hotel Booking & Car Rental plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content via unfiltered_html Grant to Customer Role in all versions up to, and including, 3.0.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires WooCommerce to be active, but since the customer role is freely self-registerable without admin approval, exploitation is effectively possible by any unauthenticated visitor who registers a WooCommerce account. While the plugin's own listing-page templates sanitize output with wp_kses_post(), the stored payload is returned unsanitized via the unauthenticated GET /wp-json/wp/v2/comments REST endpoint (content.rendered) and post/comment RSS feeds, exposing any headless client, feed reader, or third-party widget that renders comment content.
Netgate pfSense CE versions through 2.9.0 have a newline injection vulnerability in the services_pppoe_edit.php component. This flaw allows privileged users with the PPPoE Server Edit privilege to inject entries into the mpd.secret file via unvalidated username POST fields. By injecting a secret line beginning with '!', attackers can cause the mpd5 daemon to execute commands as root when a PPPoE client authenticates.
CVE-2026-58390 is a cross-site scripting (XSS) vulnerability in the OPNsense core firewall platform prior to version 26.1.11. It affects the OpenVPN connection-status dashboard widget and view, where a client common_name is inserted into HTML attributes without proper quote-safe encoding. Exploitation requires an OpenVPN server configured with username-as-common-name and RADIUS or LDAP authentication, plus the ability to provision or self-register a username containing a double quote. An authenticated client can inject script that executes in an administrator's session when viewing the dashboard or connection-status page. The vulnerability allows reading config.xml, invoking privileged APIs, resetting the root password, and obtaining root command execution. This issue is fixed in version 26.1.11.
A path traversal vulnerability (CWE-22) exists in OPNsense core prior to version 26.1.11. The OpenVPN Client Specific Override common_name field improperly accepts path traversal sequences, allowing an authenticated user with Client Specific Override privileges to cause OpenVPN configuration files to be written outside the intended directory. This occurs because the value is concatenated into a file path without normalization or basename checks. Exploitation requires triggering a matching OpenVPN client-connect or authentication event. The vulnerability is fixed in version 26.1.11.
CVE-2026-102469 is a critical vulnerability in Eclipse Vert.x's DB2 client component (vertx-db2-client) affecting versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and version 5.2.0. The vulnerability arises from unsafe deserialization of User Defined Type (UDT) column data using Java's ObjectInputStream.readObject() without any filtering or class allowlisting. This unsafe deserialization can be triggered by a malicious or man-in-the-middle DRDA server sending a crafted response with a 0x50-tagged column, which legitimate DB2 servers do not send. Exploitation can lead to remote code execution if a suitable Java deserialization gadget chain is present, or denial of service otherwise. TLS is disabled by default, increasing the risk of man-in-the-middle attacks.
Trisolutions BRPerfX version 1.4.4.0 contains a vulnerability where LDAP credentials are exposed in plaintext within the administrative configuration interface. An authenticated administrator can view these credentials by inspecting client-side code. This exposure can lead to credential compromise without requiring privilege escalation or user interaction.
Eclipse Vert.x versions 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and 5.2.0 contain a vulnerability in the vertx-mail-client component. The issue arises because CR (\r) and LF (\n) characters in user-supplied email header names and values are not sanitized before being written into the SMTP DATA section. This allows an attacker controlling these inputs to inject arbitrary email headers or manipulate the message body. Additionally, MIME part metadata fields are also affected by this lack of validation. A secondary weakness permits a bare LF in a From display-name to bypass encoding and be sent unchanged. Exploitation requires the attacker to control header or attachment metadata fields passed to the mail client, such as through a web form or API. The vulnerability has a CVSS 4.0 score of 6.9 (medium severity).
A double free vulnerability exists in the OpenSSH client shipped with Red Hat products when operating in FIPS mode during Diffie-Hellman Group Exchange (DH-GEX) key exchange. A malicious SSH server can exploit this flaw to cause the client process to terminate unexpectedly, resulting in a denial of service (DoS). The impact is limited to the availability of the SSH client process and does not lead to broader system compromise. Exploitation requires the user to connect to a malicious or compromised SSH server. Mitigation involves configuring the SSH client to avoid negotiating the vulnerable key exchange algorithm.