HFS2 version 2.4.0 and earlier contains an unauthenticated arbitrary file access vulnerability that allows unauthenticated attackers to read, write, append, and delete files anywhere the HFS service account has filesystem access outside the shared folder. Attackers can exploit the macro dispatcher's lack of authorization model combined with the path resolver's failure to confine absolute paths to manipulate the template engine and compromise the confidentiality, integrity, and availability of the host.
An assertion failure occurs in the DNS stub resolver component when processing a long search domain. This vulnerability is identified as CVE-2026-8674 and affects Microsoft products versions 3.0 and 4.0. No CVSS score or detailed impact information is provided. There is no indication of known exploitation in the wild or available patches at this time.
vm2 is a sandbox for running untrusted Node.js code. In versions >= 3.11.4 and <= 3.11.6, the NodeVM constructor computes `hasRealRequireConfig` with `typeof requireOpts === 'object' && requireOpts !== null`, so an array-shaped `require` value (for example `require: []`) satisfies the guard that is meant to reject nesting without an explicit require configuration. `makeResolverFromLegacyOptions()` then destructures the array into undefined option fields and returns a resolver containing only `NESTING_OVERRIDE.vm2`. As a result, an attacker who can supply JavaScript executed by a NodeVM configured with truthy `nesting` and an array-shaped `require` (e.g. `new NodeVM({nesting: true, require: []})`) can require the host `vm2` module, create an inner NodeVM with an attacker-chosen builtin allowlist (such as `child_process`), and execute arbitrary commands with the privileges of the host Node.js process, escaping the sandbox. Outer builtin restrictions do not constrain the attacker-created inner NodeVM. This issue is fixed in vm2 3.11.7.
Nodemailer before 9.1.0 fails to apply UTS-46 normalization when encoding international domain names, causing the domain resolver to compute a different Punycode A-label than standards-compliant parsers. Attackers can craft recipient addresses with invisible characters or compatibility mappings that pass domain allow-list checks but are delivered to attacker-controlled domains via SMTP.
CVE-2026-19668 is a vulnerability in ISC BIND 9 recursive resolver where processing large numbers of certain invalid DNSSEC records can cause excessive resource consumption. Default limits on "max-records-per-type" and "max-types-per-name" provide some mitigation. This affects multiple BIND 9 versions from 9.11.0 through 9.21.25 and their respective S1 variants.
CVE-2026-85501 affects NLnet Labs Unbound DNS resolver up to version 1.26.0 and involves allocation of resources without limits or throttling, leading to potential service degradation. The vulnerability arises from algorithmic complexity attacks on DNSSEC validation, including multiple attack vectors such as TagTrap, DelegationTrap, NsecTrap, and AdditionalTrap. These exploit excessive or malformed DNSSEC-related records to cause high computational overhead and resource exhaustion. The CVSS score is 5.3, indicating a medium severity impact primarily on availability. No known exploits are reported in the wild. No official patch or vendor advisory is provided in the input data, so patch status is not confirmed.
CVE-2026-123586 affects the Hickory resolver's recursive resolver component, where cyclic glueless sibling delegations cause the resolver to repeatedly query the same zones without stopping. This leads to excessive upstream queries per client request. The issue is fixed in version 0.26.2 by tracking zones on the resolution stack and preventing re-entry into already visited zones.
The Hickory resolver's recursive resolver component (hickory-recursor) prior to version 0.26.2 could be abused via referrals listing many glueless name servers. The resolver would recursively query all listed name servers without per-query limits, potentially causing resource exhaustion. This vulnerability was fixed in version 0.26.2 by limiting recursion to 5 glueless name servers per delegation and 200 upstream queries per client request.
The Divi theme for WordPress is vulnerable to Stored Cross-Site Scripting via the Dynamic Content feature's legacy JSON format in all versions up to, and including, 4.27.6. This is due to two compounding flaws: (1) the save-time sanitization filter `et_builder_sanitize_dynamic_content_fields()` only searches for dynamic content markers in the `@ET-DC@...@` format, but the rendering engine also supports a legacy JSON format that is silently converted at render time, completely bypassing the save-time filter, and (2) the `post_meta_key` resolver in `et_builder_filter_resolve_default_dynamic_content()` does not apply `wp_kses_post()` to the resolved meta value when `enable_html` is set to `on`, passing raw `get_post_meta()` output directly to the page. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in ash-project ash_typescript allows an attacker who controls a path-parameter value to redirect a generated client's request, and the credentials attached to it, to an unintended route or an external origin.
The URL builders in lib/ash_typescript/typed_controller/codegen/route_renderer.ex replace each :param placeholder with a bare template interpolation and never call encodeURIComponent, so the value reaches executeTypedControllerRequest raw. A value containing ../ is normalised away by the fetch URL resolver and reaches a different route, while ? or # truncates the path and can smuggle or override query parameters. For a route whose path begins with a parameter, a value such as /evil.example.com/x yields the protocol-relative URL //evil.example.com/x, sending the request and the credentials from TypedControllerConfig to an attacker-controlled host. Nothing constrains the value at runtime: get_path_param_type/2 emits only a TypeScript type, which is erased.
The query-string path is unaffected, since URLSearchParams.set encodes its own values.
This issue affects ash_typescript: from 0.15.0 before 0.18.0.
Apache Wicket enforces the upload limits configured on a form or upload field while parsing a multipart request with Apache Commons FileUpload. If the request body has already been consumed by another component, Commons FileUpload returns no items and Wicket falls back to reading the upload through HttpServletRequest#getParts(). The per-file size limit (for example Form#setFileMaxSize) and the file count limit (Form#setFileCountMax) are not applied to the parts obtained that way, and no exception is raised, so the upload is processed as though those limits had been satisfied. A remote uploader can therefore submit files that are larger, or more numerous, than the application permits, up to whatever the component that parsed the request allows. A part carrying no Content-Type header is additionally read into memory in full during parsing, so the size of that allocation is determined by the request and bounded only by those same external limits.
The total upload size limit (Form#setMaxSize) is not affected. Commons FileUpload compares the declared Content-Length against it before reading the body, so a request declaring an oversized length is rejected before the fallback is reached.
The fallback is reached in deployments where a servlet or filter has already parsed the request body — for example a servlet annotated with @MultipartConfig, Spring Boot's multipart resolver, or any filter that calls HttpServletRequest#getParameter() on a multipart request. It applies to the Wicket components that accept uploads on that path, including Form with FileUploadField, FileUploadToResourceField and AjaxFileDropBehavior. Applications that configure neither a per-file nor a file-count limit are not affected, as Wicket applies neither by default.
This issue affects Apache Wicket: from 8.0.0 through 8.18.0, from 9.0.0 through 9.23.0, from 10.0.0 through 10.10.0.
Users are recommended to upgrade to version 8.19.0, 9.24.0 or 10.11.0, which fix the issue. Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. As a workaround, configure equivalent limits in the component that parses the request — for example spring.servlet.multipart.max-file-size and max-request-size, or maxFileSize and maxRequestSize in @MultipartConfig or in the web.xml <multipart-config> element.
CVE-2026-81633 is an improper input validation vulnerability in ash-project's ash_graphql component. An unauthenticated client can send a specially crafted relay node query that triggers an unhandled KeyError, causing the resolver to crash and potentially exposing a stacktrace. This occurs because the type segment of a decoded global ID is not validated before being used as a key in a map fetch operation. The issue affects versions from 0.27.0 up to but not including 1.11.0.
Multiple security vulnerabilities have been fixed in c-ares with the update to version 1.34.8. These include several use-after-free flaws and denial of service issues related to DNS query handling and name compression. The update addresses remote code execution risks and CPU/memory exhaustion attacks. The vulnerabilities affect the c-ares DNS resolver library and have been patched in the latest release.
Multiple ClickFix malware campaigns have been identified using three delivery methods: MSI packages with DLL sideloading, NodeJS-executed JavaScript, and Python 3.5 payload execution. These campaigns use aggressive social engineering, including phone calls directing victims to compromised WordPress sites. Post-compromise activities include extensive system discovery and Active Directory enumeration. The campaigns share infrastructure and tactics linked to the Lorem Ipsum malware family and Vanilla Tempest adversary, with potential ransomware deployment as a final goal.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (deb78208f7aa932298e92a8c241ed970296c567a273fc21013dd83bb7916e81b)
On `npm install`, package.json's preinstall hook runs index.js which harvests installer host identifiers — os.hostname(), os.userInfo() username, local IPv4 addresses, home directory, INIT_CWD, public IP (fetched from api.ipify.org / icanhazip.com / ifconfig.me), DNS resolver IP/subnet, and the parent project's package.json metadata (name, author, repository, homepage) — and transmits them to the hardcoded Interactsh-style callback host `da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun`. Exfiltration uses two channels: an HTTPS/HTTP POST to `/poc/<uuid>` on the callback host, and a hex-encoded DNS covert channel that splits the JSON payload into ≤60-character subdomain labels resolved against the callback host, designed to bypass egress filters that block outbound HTTP but permit DNS. The version number (999.9.12) and package name are consistent with a dependency-confusion probe.
## Source: ossf-package-analysis (d7cde5bd15beab8488f3b3b6bde2f17fff6c148ef2d575613762f337bd1c8281)
The OpenSSF Package Analysis project identified 'fund-list-filter' @ 999.9.12 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.