The scanFeedsResolver in packages/api/src/resolvers/subscriptions/index.ts passes the caller-supplied url straight to axios.get(url, rssParserConfig()) with no address validation. The same file guards the subscribe path with validateUrl(), which rejects private and reserved ranges through the private-ip library, and createPageSaveRequest applies the same check, so the omission is specific to this resolver. An authenticated user can direct the server to request arbitrary internal endpoints. The response is parsed as a feed or as HTML and the resolver returns the resulting url, title, description and type fields, so disclosure is limited to feed-shaped metadata and to link elements advertising RSS or Atom feeds; requests that do not parse still distinguish reachable ports from unreachable ones through the resulting error.
CVE-2026-17097 is a vulnerability in IBM PowerVM Hypervisor affecting multiple firmware versions. It involves improper validation of array indices in the hypervisor call interface. An attacker with root access to a guest partition can exploit this flaw to cause a virtual processor to become permanently unresponsive, requiring a full platform reboot. Additionally, exploitation may lead to unintended data injection into hypervisor or partition memory without attacker control over the target location. The vulnerability impacts system integrity and availability.
CVE-2026-16849 is a medium severity vulnerability in IBM AIX versions 7.2 and 7.3, and IBM PowerVM VIOS 4.1. It involves improper validation of an array index boundary, which could allow a remote attacker to cause a denial of service. The vulnerability does not impact confidentiality or integrity but affects availability. No known exploits are reported in the wild. No patch or remediation details are provided in the available data.
CVE-2026-55564 is an out-of-bounds read vulnerability in FreeRDP versions prior to 3.27.0. The flaw exists in the glyph_cache_get function, which incorrectly checks an index against cache->number, allowing a malicious RDP server to cause a read beyond the bounds of an array. This can lead to client crashes and potential disclosure of adjacent heap memory. The issue is fixed in FreeRDP version 3.27.0.
Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. Prior to 8.21.0, a ${...} expression or backtick in a query parameter default is emitted into a module-level template literal emitted by zod schema generation without safe encoding. This permits attacker-controlled JavaScript to be evaluated when the generated zod schema module is imported, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/zod/src/index.ts function formatDefaultValue. This issue is fixed in version 8.21.0.
Orval generates type-safe JavaScript clients in TypeScript from OpenAPI v3 and Swagger v2 specifications. From version 8.19.0 until 8.21.0, a double quote in a schema property name is emitted into the generated zod.object({...}) schema without safe encoding. This permits attacker-controlled JavaScript to be evaluated when the generated zod schema module is imported, resulting in code execution in the developer, CI, test, or application environment. The affected code is packages/zod/src/index.ts and zod object-key generation. This issue is fixed in version 8.21.0.
FFmpeg before commit 65b0dab contains an out-of-bounds read in the DASH demuxer (libavformat/dashdec.c). When a live DASH manifest is refreshed with a startNumber that is lower than the previous value, the current sequence number is driven negative. The fragment retrieval function checked only the upper bound before indexing the fragments array, allowing a negative index to be used and causing an out-of-bounds read. A malicious or misconfigured DASH server can trigger this by serving a live manifest with a decreasing startNumber across a manifest refresh.
Grav Flex Objects Plugin allows you to build custom collections of objects. Prior to 1.4.3, the Grav Flex Objects Admin Next API requireFlexPermission() method in classes/Api/FlexApiController.php returns without denying access when a directory blueprint omits config.admin.permissions. An authenticated account with only api.access can use the index, show, create, update, delete, export, and media handlers for a permission-less directory even though the core admin.flex-object. authorization fallback would deny the same actions. This issue is fixed in version 1.4.3.
GitPython versions before 3.1.58 have an arbitrary file overwrite vulnerability due to improper neutralization of argument delimiters in certain methods. This allows attackers to inject the --index-output option into git commands, enabling overwriting of arbitrary files with git-index blobs at writable paths controlled by the attacker.
phpMyFAQ versions before 4.1.7 have a missing authorization vulnerability in the admin API read endpoints related to LDAP, Elasticsearch, OpenSearch, and dashboard configuration. This flaw allows any authenticated user to access sensitive administrative data without proper permission checks. Exploitation can reveal LDAP server topology, bind account names, search bases, index statistics, and site analytics.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (d3c551a6031e48a54b550a604e2198a4491cf935407744bba8ef0c11c54086c4)
The package advertises EVM address validation but performs no local validation. Its single exported function validated(e) in index.js issues axios.get against a hardcoded destination and appends the caller-supplied argument to the URL, causing whatever the consuming application passes in (EVM addresses, keys, or arbitrary user data) to be transmitted to a remote host the caller never configured. The destination is deliberately hidden: a scrambled string array is joined, ROT13-transformed, and reversed at runtime to reconstruct https://api-ivalidte.vercel.app/app/api/ — a typosquat-shaped Vercel host that does not correspond to any documented service for this package. The obfuscation of the destination combined with the mismatch between the advertised purpose (local validation) and the actual behavior (remote relay to an author-controlled endpoint) is the silent-relay shape.
A vulnerability exists in the ktls_ocf_tls_cbc_decrypt() function when processing TLS 1.2 CBC records. The function incorrectly increments the iovec index for every mbuf in the chain, including those containing only TLS header bytes, leaving uninitialized entries in the iovec array. This uninitialized memory can be read during HMAC computation, potentially causing a kernel panic. Exploitation requires a remote TLS peer to control TCP segmentation so that the first mbuf of a CBC record contains only the TLS record header.