Prior to version 26.10.0rc1, the Twisted framework's DNSDatagramProtocol component accepts UDP DNS responses based solely on matching the 16-bit transaction ID without verifying the source host and port. This allows an attacker who can send packets to the resolver's listening port with the correct transaction ID to inject forged DNS answers. Such forgery can redirect hostname resolution, potentially enabling mail interception, server-side request forgery, or man-in-the-middle attacks. The issue is fixed in version 26.10.0rc1.
CVE-2026-79981 is a medium severity vulnerability in the Zephyr project's DNS stub resolver affecting versions from 1.8.0 up to but not including 4.5.0. The resolver uses a fixed source UDP port per server for DNS queries, violating RFC 5452's requirement that both source port and transaction ID vary. This allows an off-path attacker with UDP reachability to flood forged DNS responses and potentially cause the application to resolve attacker-chosen addresses. The vulnerability is mitigated by a fix in version 4.5.0 that randomizes the source port per query, increasing the guessing space and reducing attack feasibility.
A denial of service vulnerability exists in GraphQL-core's OverlappingFieldsCanBeMerged validation rule, which can be exploited by a crafted query causing quadratic to worst-case O(n²·m²) validation time. This can exhaust CPU resources for minutes on a single core during validation, without requiring authentication or exposing data. The issue affects default settings of GraphQL-core based servers. The vulnerability is fixed in versions 3.2.12 and 3.3.0rc1 by enforcing a comparison budget that aborts validation on excessive complexity.
Incorrect authorization checks in Amazon Athena engine version 3 query processing could have allowed an authenticated user to read AWS account identifiers and SQL statement text query metadata from other AWS accounts. Query results, and data stored in Amazon S3 or other data sources, were not accessible through this issue.
AWS remediated the issue on October 7, 2026. No customer action is required.
CVE-2026-114460 is an off-by-one pointer calculation error in the pbuchbinder mod_qos module. This flaw occurs when merging request body parameters with an existing URL query, causing the query string to be truncated during security evaluation while the actual request remains unchanged. An unauthenticated remote attacker could exploit this by submitting a crafted request that hides prohibited values from inspection, bypassing configured security rules. Red Hat has assessed that this vulnerability does not affect any currently supported Red Hat products.
OpenRemote versions from 1.2.0 up to but not including 1.31.0 have a missing authorization vulnerability in the GatewayServiceResource. This flaw allows any authenticated user, without requiring administrative privileges, to start, stop, and query gateway tunnels. Exploitation involves sending POST or DELETE requests to the gateway tunnel endpoint, enabling attackers to open persistent bidirectional TCP circuits into an edge gateway's network or to tear down operator tunnels.
Electron versions prior to 42.11.1, 43.5.1, 44.1.1, and 45.0.0-alpha.4 have a missing authorization vulnerability where chrome.tabs.query() exposes each tab's URL and title to extensions without the required permissions. This allows an untrusted extension loaded via session.extensions.loadExtension to access sensitive browsing information. The issue is fixed in the specified versions.
CVE-2026-97313 is a reachable assertion vulnerability in ISC BIND 9 that can cause the server to exit unexpectedly, resulting in a denial of service. The issue occurs when a recursive BIND server receives a query with recursion desired (RD=1) followed by a non-recursive query (RD=0), under specific configuration conditions involving RPZ zones. This affects BIND 9 versions from 9.16.0 through 9.18.50, 9.20.0 through 9.20.29, 9.21.0 through 9.21.26, and certain S1 builds. The vulnerability requires the server to allow recursive queries and have at least two RPZ zones configured with differing "recursive-only" settings.
CVE-2026-60964 is a low-severity vulnerability in Oracle PeopleSoft Enterprise PeopleTools (Open Query component) versions 8.61 and 8.62. It requires a high-privileged attacker with logon access to the infrastructure where PeopleSoft runs. Successful exploitation could allow unauthorized read access to some PeopleSoft accessible data. The vulnerability is difficult to exploit and does not impact integrity or availability.
ApostropheCMS versions prior to 4.33.0 and passport-bridge versions prior to 1.6.1 contain a vulnerability where a single-use bearer session token is placed in a redirect URL during cross-host or cross-locale session migration. This allows a client who obtains and redeems a still-valid, unconsumed token before its first use to adopt the associated session. The issue is fixed in ApostropheCMS 4.33.0 and passport-bridge 1.6.1.
## Summary
ApostropheCMS widget styles support project-defined schema fields. If a project defines a free-form `string` style field with a CSS `property` and no selector, an editor-controlled value is rendered as an inline CSS declaration. The resulting declaration is then inserted into the widget wrapper's `style="..."` attribute without HTML-attribute escaping.
An attacker who can edit the widget can include a double quote in the style value, terminate the `style` attribute, and inject new HTML event-handler attributes. The payload is stored with the widget and executes in the Apostrophe site origin whenever the affected published page is rendered.
This is a sibling of CVE-2026-33889 / `GHSA-97v6-998m-fp4g`. The earlier issue escaped from a `<style>` element through a malicious color value. This variant reaches a different sink related to the automatically generated widget wrapper's inline `style` and `class` attributes.
## Details
### Root Cause 1: Free-form string style values retain HTML metacharacters
The standard string field converter uses `launder.string()` and length validation. This performs type normalization, not output encoding for an HTML attribute context:
[`packages/apostrophe/modules/@apostrophecms/schema/lib/addFieldTypes.js:296-333`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/schema/lib/addFieldTypes.js#L296-L333)
```javascript
self.addFieldType({
name: 'string',
// ...
convert(req, field, data, destination) {
destination[field.name] = self.apos.launder.string(data[field.name]);
destination[field.name] = checkStringLength(
destination[field.name],
field.min,
field.max
);
}
});
```
Quotes therefore remain in a value supplied through a style field.
### Root Cause 2: The value is converted into inline CSS without value validation
For a field with `property` but no `selector` or media query, `renderScopedStyles()` selects inline rendering. The generic extractor concatenates the configured property and editor-controlled value:
[`packages/apostrophe/modules/@apostrophecms/styles/ui/apos/universal/render.mjs:171-228`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/styles/ui/apos/universal/render.mjs#L171-L228)
[`packages/apostrophe/modules/@apostrophecms/styles/ui/apos/universal/render.mjs:598-647`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/styles/ui/apos/universal/render.mjs#L598-L647)
```javascript
rule = `${property}: ${normalized.value}${normalized.unit}`;
// ...
if (isInline) {
return {
css: '',
classes: [ ...storage.classes ],
inline: stringifyRules(storage.styles, true)
};
}
```
For example, the value below becomes part of a `font-family` declaration:
```text
serif" tabindex="0" autofocus onfocus="document.body.dataset.inline='executed'
```
### Root Cause 3: Attribute values are serialized without HTML escaping
`getWidgetAttributes()` places the inline CSS into an attribute tuple, then concatenates every tuple into `key="value"` without encoding `&`, `<`, `>`, `'`, or `"`:
[`packages/apostrophe/modules/@apostrophecms/styles/lib/methods.js:251-322`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/styles/lib/methods.js#L251-L322)
```javascript
if (styleParts.length) {
attrs.push(
[ 'style', `${styleParts.join(';')};` ]
);
}
if (options.asObject) {
return Object.fromEntries(attrs);
}
return attrs
.map(([ key, value ]) => `${key}="${value}"`)
.join(' ');
```
The same raw serializer also makes a project-defined free-form `string` style with `class: true` a potential sibling path, because the string is added to `classes` and later serialized into `class="..."`. The inline-property path was the path dynamically verified.
### Root Cause 4: The unsafe string is used by the automatic public wrapper
Styled widgets use `getWidgetAttributes()` to create a wrapper around the rendered widget:
[`packages/apostrophe/modules/@apostrophecms/widget-type/index.js:448-457`](https://github.com/apostrophecms/apostrophe/blob/aa5170c7df9ff9ea5ac2e72a008f12e28dae6ca8/packages/apostrophe/modules/%40apostrophecms/widget-type/index.js#L448-L457)
```javascript
if (hasStyles && self.options.stylesWrapper !== false) {
const styles = self.apos.styles.prepareWidgetStyles(widget);
const styleTag = self.apos.styles
.getWidgetElements(styles, { scene: req.scene });
const wrapperAttrs = self.apos.styles.getWidgetAttributes(styles);
return `${styleTag}<div${wrapperAttrs ? ' ' + wrapperAttrs : ''}>${markup}</div>`;
}
```
Consequently, the injected attribute is present on normal public page renders, not only in the editor UI.
### Why the CVE-2026-33889 defense does
CVE-2026-112947 is a path traversal vulnerability in the Vite development server that allows an attacker to retrieve the first 4 bytes of arbitrary files on disk by sending a request with the query parameter '?vite-wasm-instance'. This occurs because the internal Wasm plugin's load hook reads files without applying server.fs access restrictions. The vulnerability affects Vite versions >=0.2.8 <1.1.0, >=8.2.0 <8.2.4, and >=8.3.0 <8.3.3. It only impacts applications that expose the Vite dev server to the network, run on Node.js or Deno, and have sensitive information in the first 4 bytes of a file. The issue is fixed in versions 1.1.0, 8.2.4, and 8.3.3.
A moderate information disclosure vulnerability exists in Grafana as shipped in various Red Hat products. An authenticated user with query access to an Azure Monitor data source can misuse the resource proxy to send unauthorized requests to Azure Resource Manager APIs using the data source's configured cloud identity. This can lead to information disclosure limited to the scope of the identity's permissions. The flaw does not impact integrity or availability. Red Hat has deferred the fix for affected products due to the moderate impact and prerequisites of authentication and query access. A fix is being pursued for Red Hat Hardened Images and Fedora builds.
WhoDB versions from 0.104.0 up to but not including 0.135.0 contain a critical path traversal vulnerability. This flaw allows remote attackers to read and write arbitrary files on the host by leveraging DuckDB filesystem functions via the query editor without requiring credentials. Exploitation can lead to theft of sensitive files such as session keys and stored database credentials, or overwriting of files. The vulnerability is fixed in version 0.135.0.
The Hippoo Mobile App for WooCommerce WordPress plugin is vulnerable to reflected cross-site scripting (XSS) via the 'token_id' parameter in all versions up to and including 1.12.0. This vulnerability arises from insufficient input sanitization and output escaping, allowing unauthenticated attackers to inject arbitrary scripts that execute when a user interacts with a crafted link. The vulnerability bypasses URL path regex constraints due to query-string parameter precedence in WP_REST_Request.