js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an attacker to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default).

The remote Fedora 45 host has packages installed that are affected by multiple vulnerabilities as referenced in the FEDORA-2026-a8a5f6b41b advisory.

    Latest Ansible 13

    - Close bogus CVEs

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 43 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-085abeea02 advisory.

    Refresh vendor bundle, fixes CVE-2026-4800.

    ----

    Update vendor bundle.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 42 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-b8aad5411e advisory.

    Update vendor bundle.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 44 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2026-db0c5d039c advisory.

    Update vendor bundle.

Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:20251-1 advisory.

    Update to version 4.7.

    Security issues fixed:

    - CVE-2025-13465: prototype pollution in the _.unset and _.omit functions can lead to deletion of methods     from global       (bsc#1257325).
    - CVE-2025-64718: js-yaml prototype pollution in merge (bsc#1255425).

    Other updates and bugfixes:

    - version update to 4.7

      * Translation updates

    - version update to 4.6:

      * Translation updates
      * Dependency updates
      * Fix translations pot file not being update

    - version update to 4.5:

      * Dependency updates

    - version update to 4.4:

      * Translation updates
      * Dependency updates

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0978 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-68429:
    Storybook is a frontend workshop for building user interface components and pages in isolation. A     vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10     relates to Storybooks handling of environment variables defined in a `.env` file, which could, in     specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by     the `storybook build` command. When a built Storybook is published to the web, the bundles source is     viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be     vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly)     in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built     Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including     common CI-based builds where secrets are provided via platform environment variables rather than `.env`     files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that     share a repo with your Storybook are not affected. Users should upgrade their Storybookon both their     local machines and CI environmentto version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible.
    Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files     and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of     this issue and will need to change how they reference environment variables after this update. If a     project can no longer read necessary environmental variable values, either prefix the variables with     `STORYBOOK_` or use the `env` property in Storybooks configuration to manually specify values. In     either case, do not include sensitive secrets as they will be included in the built bundle.

    CVE-2025-64718:
    js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker     to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All     users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users     can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in     Deno, pollution protection is on by default).

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - js-yaml is a JavaScript YAML parser and dumper. In js-yaml before 4.1.1 and 3.14.2, it's possible for an     attacker to modify the prototype of the result of a parsed yaml document via prototype pollution     (`__proto__`). All users who parse untrusted yaml documents may be impacted. The problem is patched in js-     yaml 4.1.1 and 3.14.2. Users can protect against this kind of attack on the server by using `node
    --disable-proto=delete` or `deno` (in Deno, pollution protection is on by default). (CVE-2025-64718)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Severity
315971	Fedora 45 : ansible / ansible-core (2026-a8a5f6b41b)	Nessus	Fedora Local Security Checks	critical
306054	Fedora 43 : yarnpkg (2026-085abeea02)	Nessus	Fedora Local Security Checks	critical
302754	Fedora 42 : yarnpkg (2026-b8aad5411e)	Nessus	Fedora Local Security Checks	medium
302529	Fedora 44 : yarnpkg (2026-db0c5d039c)	Nessus	Fedora Local Security Checks	medium
299734	openSUSE 16 Security Update : cockpit-repos (openSUSE-SU-2026:20251-1)	Nessus	SuSE Local Security Checks	high
282602	TencentOS Server 4: grafana (TSSA-2025:0978)	Nessus	Tencent Local Security Checks	high
275394	Linux Distros Unpatched Vulnerability : CVE-2025-64718	Nessus	Misc.	medium

Detections

Analytics

CVE-2025-64718

medium

Tenable Plugins

critical

critical

medium

medium

high

high

medium