Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through 4.7.8, the Handlebars CLI precompiler (`bin/handlebars` / `lib/precompiler.js`) concatenates user-controlled strings — template file names and several CLI options — directly into the JavaScript it emits, without any escaping or sanitization. An attacker who can influence template filenames or CLI arguments can inject arbitrary JavaScript that executes when the generated bundle is loaded in Node.js or a browser. Version 4.7.9 fixes the issue. Some workarounds are available. First, validate all CLI inputs before invoking the precompiler. Reject filenames and option values that contain characters with JavaScript string-escaping significance (`"`, `'`, `;`, etc.). Second, use a fixed, trusted namespace string passed via a configuration file rather than command-line arguments in automated pipelines. Third, run the precompiler in a sandboxed environment (container with no write access to sensitive paths) to limit the impact of successful exploitation. Fourth, audit template filenames in any repository or package that is consumed by an automated build pipeline.

According to its self-reported version, the Nessus Network Monitor running on the remote host is prior to 6.5.4. It is, therefore, affected by multiple vulnerabilities as referenced in the TNS-2026-14 advisory.

  - An integer overflow can be triggered in SQLite's `concat_ws()` function. The resulting, truncated integer     is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the     original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can     result in arbitrary code execution. (CVE-2025-3277)

  - When using `CURLOPT_PINNEDPUBLICKEY` option with libcurl or `--pinnedpubkey` with the curl tool,curl     should check the public key of the server certificate to verify the peer. This check was skipped in a     certain condition that would then make curl allow the connection without performing the proper check, thus     not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2     built to use GnuTLS and the user had to explicitly disable the standard certificate verification.
    (CVE-2025-13034)

  - When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread     would inadvertently change them globally and therefore possibly also affect other concurrently setup     transfers. Disabling certificate verification for a specific transfer could unintentionally disable the     feature for other threads as well. (CVE-2025-14017)

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-6599e30e04 advisory.

    33.0.3 Release

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-cb5661d883 advisory.

    33.0.3 Release

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-2fed8dd674 advisory.

    33.0.3 Release

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through     4.7.8, the Handlebars CLI precompiler (`bin/handlebars` / `lib/precompiler.js`) concatenates user-     controlled strings  template file names and several CLI options  directly into the JavaScript it emits,     without any escaping or sanitization. An attacker who can influence template filenames or CLI arguments     can inject arbitrary JavaScript that executes when the generated bundle is loaded in Node.js or a browser.
    Version 4.7.9 fixes the issue. Some workarounds are available. First, validate all CLI inputs before     invoking the precompiler. Reject filenames and option values that contain characters with JavaScript     string-escaping significance (``, `'`, `;`, etc.). Second, use a fixed, trusted namespace string passed     via a configuration file rather than command-line arguments in automated pipelines. Third, run the     precompiler in a sandboxed environment (container with no write access to sensitive paths) to limit the     impact of successful exploitation. Fourth, audit template filenames in any repository or package that is     consumed by an automated build pipeline. (CVE-2026-33941)

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

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Handlebars provides the power necessary to let users build semantic templates. In versions 4.0.0 through
    4.7.8, the Handlebars CLI precompiler (`bin/handlebars` / `lib/precompiler.js`) concatenates user-
    controlled strings — template file names and several CLI options — directly into the JavaScript it emits,
    without any escaping or sanitization. An attacker who can influence template filenames or CLI arguments
    can inject arbitrary JavaScript that executes when the generated bundle is loaded in Node.js or a browser.
    Version 4.7.9 fixes the issue. Some workarounds are available. First, validate all CLI inputs before
    invoking the precompiler. Reject filenames and option values that contain characters with JavaScript
    string-escaping significance (`"`, `'`, `;`, etc.). Second, use a fixed, trusted namespace string passed
    via a configuration file rather than command-line arguments in automated pipelines. Third, run the
    precompiler in a sandboxed environment (container with no write access to sensitive paths) to limit the
    impact of successful exploitation. Fourth, audit template filenames in any repository or package that is
    consumed by an automated build pipeline. (CVE-2026-33941)

ID	Name	Product	Family	Severity
314931	Nessus Network Monitor < 6.5.4 Multiple Vulnerabilities (TNS-2026-14)	Nessus	Misc.	medium
313733	Fedora 43 : nextcloud (2026-6599e30e04)	Nessus	Fedora Local Security Checks	medium
313662	Fedora 44 : nextcloud (2026-cb5661d883)	Nessus	Fedora Local Security Checks	medium
313661	Fedora 42 : nextcloud (2026-2fed8dd674)	Nessus	Fedora Local Security Checks	medium
304160	Linux Distros Unpatched Vulnerability : CVE-2026-33941	Nessus	Misc.	high
439364	SCA: security update for handlebars (GHSA-xjpj-3mr7-gcpf)	Tenable Cloud Security	SCA Checks	high
439364	SCA: security update for handlebars (GHSA-xjpj-3mr7-gcpf)	Tenable Self-Hosted Container Security	SCA Checks	high

Detections

Analytics

CVE-2026-33941

high

Tenable Plugins

medium

medium

medium

medium

high

high

high