A stack overflow vulnerability exists in gfs2-utils due to unvalidated use of an inode height value from on-disk metadata in the metadata walk code. This flaw can cause stack exhaustion and denial of service when processing crafted GFS2 filesystem images. The vulnerability affects multiple specific versions of gfs2-utils. The CVSS score is 4.7, indicating medium severity. No known exploits are reported in the wild. Patch status is not confirmed from the provided data.
This vulnerability in Slurm workload manager (slurm-wlm) addresses two issues: sbcast shared objects skipping credential verification and a possible slurmd crash triggered by invalid sbcast filenames. Multiple specific versions of slurm-wlm are affected. The severity is assessed as medium. No CVSS score is provided. There is no indication of known exploits in the wild or vendor patch status in the provided data.
A stack overflow vulnerability exists in slurmstepd when a job environment contains an oversized SPANK option variable. This flaw affects multiple specific versions of the slurm-wlm workload manager. The vulnerability has medium severity and no known exploits in the wild have been reported. No CVSS score is provided.
CVE-2026-65109 is a vulnerability in Slurm workload manager (slurm-wlm) where the slurmstepd component improperly removes files outside the container spool directory during OCI container cleanup and leaves spool directories behind when ContainerPath contains a task ID pattern. This issue affects multiple specific versions of slurm-wlm. The severity is assessed as medium based on the described impact.
A heap over-read vulnerability exists in slurmd component of slurm-wlm when unpacking a malformed forward data RPC, which can cause a crash. The issue also involves handling a malformed forward data RPC with a missing socket address. Multiple specific versions of slurm-wlm are affected. The severity is assessed as medium.
CVE-2026-65139 addresses multiple issues related to unsafe operations and queries in the Slurm workload manager's slurmdbd component. These issues could potentially lead to security concerns in how the database daemon processes certain operations. The vulnerability affects specific versions of slurm-wlm as listed. The severity is assessed as medium based on the available information.
A privilege escalation vulnerability in Slurm workload manager allows an operator to alter Administrator accounts through the accounting database. This issue affects multiple specific versions of Slurm. The severity is assessed as medium. No CVSS score is available. There are no known exploits in the wild. The product is not a cloud service, and no patch information is provided in the input data.
CVE-2026-65165 addresses various issues in Slurm workload manager related to job steps and discrepancies in node counts. The vulnerability affects multiple specific versions of slurm-wlm. The severity is assessed as medium. No CVSS score is provided. There is no indication of known exploits in the wild or cloud service impact. Patch or remediation status is not explicitly stated in the provided data.
An integer underflow vulnerability exists in libjxl before version 0.12 in the container box parser. This flaw allows remote attackers to inject arbitrary metadata by exploiting 64-bit box size truncation to size_t on 32-bit platforms. Crafted JPEG XL files can cause the decoder to misinterpret attacker-controlled bytes as phantom box headers, enabling injection of metadata such as Exif, XMP, IPTC, and JUMBF, and may lead to out-of-bounds reads.
A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.
A flaw was found in rpm. An attacker can exploit a command injection vulnerability by influencing the path or filename of a tarball processed by `rpmbuild -t*` to include shell metacharacters. This is particularly relevant in automated build or continuous integration (CI) workflows that ingest externally supplied artifact names. Successful exploitation allows for arbitrary command execution with the privileges of the build user, which could lead to information disclosure or disruption of the build environment.
A command injection vulnerability exists in the rpmuncompress utility. This flaw allows a local attacker to execute arbitrary commands by processing specially crafted archive filenames containing shell metacharacters that are not properly escaped. Exploitation requires user interaction, such as invoking rpmuncompress on a malicious file. The vulnerability impacts confidentiality, integrity, and availability of data accessible to the invoking user.
pnpm versions 11.0.0 before 11.11.0 and 10.7.0 before 10.34.5 contain a vulnerability where environment-variable placeholders in proxy settings within pnpm-workspace.yaml are expanded improperly. This allows an attacker controlling the repository manifest to exfiltrate environment secrets such as NPM_TOKEN or GITHUB_TOKEN by causing them to be included in proxy hostnames or userinfo, routing traffic through attacker-controlled hosts. The issue occurs during configuration loading before any lifecycle scripts run. The vulnerability is fixed in pnpm 11.11.0 and 10.34.5.
A medium severity vulnerability identified as CVE-2026-80220 affects multiple specific versions of the prometheus-postgres-exporter software. The exact nature and technical details of the vulnerability are unknown based on the available information. There is no CVSS score or detailed description provided. No known exploits in the wild have been reported. The affected versions are explicitly listed, covering various builds and Ubuntu package versions.
Php nrk predis versions from 3.0.0-RC1 up to 3.3.0 contain a vulnerability in pipeline handling on aggregate cluster and replication connections. The issue arises because the RESP buffer is reparsed incorrectly by splitting on CRLF sequences instead of respecting RESP length prefixes. This allows attacker-controlled keys or values with CRLF sequences to be interpreted as additional commands, enabling unauthorized operations such as shard-wide cache deletion, data modification, data reads, or node disruption. The vulnerability affects only the pipeline() method; transaction() and MULTI are not impacted. The issue is fixed in version 3.3.0.
A vulnerability in kamailio version 6.1.1 and earlier allows a remote attacker to cause a denial of service via the IMS P-CSCF registration handling components. The issue affects multiple specific kamailio package versions. The CVSS v3.1 score is 7.5, indicating a medium severity denial of service impact with no confidentiality or integrity loss.
An issue in kamailio v.6.1.1 and before allows a remote attacker to cause a denial of service via the ims_registrar_pcscf module, specifically the pcscf_save_pending/save_pending path and security-agreement parsing in sec_agree.c:parse_sec_agree()
A vulnerability exists in node-xmldom prior to versions 0.8.15 and 0.9.12, and in xmldom version 0.6.0 and earlier, where the DOCUMENT_TYPE_NODE branch in lib/dom.js improperly validates the DocumentType.name property. This allows injection of sibling markup by terminating the <!DOCTYPE ...> declaration early if the name contains '>' or whitespace. The issue is fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom 0.6.0 and earlier.
The node-xmldom library versions from 0.9.0 up to 0.9.12 contain a vulnerability in the shared reg() builder in lib/grammar.js. This builder compiles the anchored QName_exact validator with the multiline flag, causing ^ and $ anchors to validate only one line instead of the entire XML name. As a result, certain XML creation functions accept malformed XML names that include line terminators, potentially injecting markup when serialized. This issue is fixed in version 0.9.12.
A vulnerability in node-xmldom versions prior to @xmldom/xmldom 0.8.15 and 0.9.12, and in xmldom 0.6.0 and earlier, allows Document.createEntityReference(name) to accept invalid names. This leads to serialization of attacker-controlled XML markup when using XMLSerializer.serializeToString() with requireWellFormed: true. Exploitation requires an application to create and serialize an EntityReference node directly. Fixed in @xmldom/xmldom versions 0.8.15 and 0.9.12; no fix is available for xmldom.