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

  - js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1,
    maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while
    processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge
    targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource
    limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in
    applications that parse untrusted YAML, and merge processing is enabled by default on these release lines.
    In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions
    3.15.2, 4.3.2, and 5.4.1. (CVE-2026-84375)

The remote Redhat Enterprise Linux 10 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2026:71113 advisory.

    Red Hat Ansible Automation Platform provides an enterprise framework for building, deploying and managing     IT automation at scale. IT Managers can provide top-down guidelines on how automation is applied to     individual teams, while automation developers retain the freedom to write tasks that leverage existing     knowledge without the overhead. Ansible Automation Platform makes it possible for users across an     organization to share, vet, and manage automation content by means of a simple, powerful, and agentless     language.

    Security Fix(es):

    * automation-controller: GitPython: Remote Code Execution via Git directory impersonation (CVE-2026-87817)
    * automation-controller: Job template enumeration via unauthenticated Bitbucket webhook oracle     (CVE-2026-84717)
    * automation-controller: Command argument injection via SystemJob extra_vars (CVE-2026-84724)
    * automation-controller: Masked credential data disclosure via workflow job node artifact search     (CVE-2026-84720)
    * automation-controller: Instance-group privilege escalation via workflow job template copy     (CVE-2026-84719)
    * automation-controller: Audit log falsification via unrestricted X-Forwarded-For trust (CVE-2026-84718)
    * automation-controller: Mesh certificate issuance for arbitrary hostnames via install bundle     (CVE-2026-84716)
    * automation-controller: Template injection via sanitize_jinja regex bypass (CVE-2026-84714)
    * automation-controller: Automation mesh topology disclosure via unauthenticated ping endpoint     (CVE-2026-84712)
    * automation-controller: Arbitrary file read via Project scm_branch git argument injection     (CVE-2026-84711)
    * automation-controller: Denial of service via credential type injector Jinja rendering (CVE-2026-84709)
    * automation-controller: Control-plane secret exposure via container group pod spec override     (CVE-2026-84708)
    * automation-controller: Unauthorized job output disclosure via host filter query traversal     (CVE-2026-84707)
    * automation-controller: Code execution via credential type environment-injector blocklist bypass     (CVE-2026-84706)
    * automation-controller: Cross-tenant credential exposure via execution environment binding     (CVE-2026-84703)
    * automation-controller: Cross-tenant execution privilege bypass via workflow job template node patch     (CVE-2026-84692)
    * automation-controller: Secret key and database credential disclosure via format-string injection     (CVE-2026-84691)
    * automation-controller: Cross-tenant job hijack via Bulk Job Launch node reference (CVE-2026-84689)
    * automation-controller: Credential token disclosure via notification template type-switch replay     (CVE-2026-84686)
    * automation-controller: Privilege escalation via constructed inventory attachment (CVE-2026-84684)
    * automation-controller: Stored cross-site scripting via ANSI hyperlink sequence in job output     (CVE-2026-84683)
    * automation-controller: Credential-use privilege escalation via organization Galaxy credential attachment     (CVE-2026-84680)
    * automation-controller: Arbitrary environment variable injection via AWX_TASK_ENV setting     (CVE-2026-84679)
    * automation-controller: Server-side request forgery via Thycotic Secret Server credential test     (CVE-2026-84644)
    * automation-controller: Cross-organization credential exposure via Project signature-validation binding     (CVE-2026-84643)
    * automation-controller: Instance-group privilege escalation via Schedule and workflow node attachment     (CVE-2026-84638)
    * automation-controller: Remote code execution via Project scm_url git argument injection (CVE-2026-84502)
    * automation-controller: Survey password disclosure via validation error message (CVE-2026-84499)
    * automation-controller: Unauthenticated scheduler-trigger endpoint exposure (regression) (CVE-2026-84486)
    * automation-controller: Privilege escalation via provisioning-callback host-match bypass (CVE-2026-84474)
    * automation-controller: Instance-group privilege escalation via Bulk Job Launch permission check     (CVE-2026-84470)
    * automation-controller: GitPython: Arbitrary file read via TagReference.create() (CVE-2026-78679)
    * automation-controller: awx: Privilege escalation to OpenShift namespace via pod_spec_override injection     in container groups (CVE-2026-75884)
    * automation-controller: Command-line argument injection via ad hoc command limit field (CVE-2026-71465)
    * automation-controller: Git argument-injection guard bypass via Schedule scm_branch prompt     (CVE-2026-71464)
    * automation-controller: Stack trace disclosure via notification-template Jinja whitelist bypass     (CVE-2026-71463)
    * automation-controller: Filesystem path-existence oracle via CUSTOM_VENV_PATHS validation     (CVE-2026-71462)
    * automation-controller: Cross-tenant job event data exposure via missing RBAC check (CVE-2026-71459)
    * automation-controller: Cross-tenant resource enumeration via Named-URL 404 response oracle     (CVE-2026-71458)
    * automation-controller: Unrestricted subscription and license information disclosure (CVE-2026-71460)
    * automation-controller: GitPython: Command Injection via Git option prefix abbreviation (CVE-2026-67325)
    * automation-controller: GitPython: Arbitrary code execution via command injection due to unguarded Git     options (CVE-2026-67323)
    * automation-controller: GitPython: Environment variable exfiltration via attacker-controlled clone URL     (CVE-2026-67322)
    * automation-controller: Kubernetes service account token exfiltration via HashiCorp Vault credential SSRF     (CVE-2026-12564)
    * automation-gateway-proxy: Golang MIME: Denial of Service via maliciously-crafted MIME header     (CVE-2026-42504)
    * automation-gateway-proxy: golang net/url: Denial of Service from quadratic complexity in path resolution     (CVE-2026-56860)
    * automation-gateway-proxy: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal     (CVE-2026-33818)
    * automation-gateway-proxy: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages     (CVE-2026-56862)
    * automation-gateway-proxy: Go html/template: Cross-Site Scripting via pathological input (CVE-2026-56858)
    * automation-platform-ui: js-yaml: Denial of Service vulnerability in YAML parsing (CVE-2026-84375)
    * automation-platform-ui: DOMPurify: Cross-Site Scripting via IN_PLACE sanitization (CVE-2026-75838)
    * automation-platform-ui: nanoid: Denial of Service via negative size input in non-secure module functions     (CVE-2026-67214)
    * automation-platform-ui: nanoid: Predictable ID generation due to integer overflow (CVE-2026-73086)
    * automation-platform-ui: PostCSS: Information disclosure via crafted sourceMappingURL (CVE-2026-69153)
    * automation-platform-ui: js-yaml: Denial of Service via crafted YAML documents (CVE-2026-59869)
    * python-sqlparse: Denial of Service via quadratic CPU consumption in SQL parsing (CVE-2026-54284)
    * python-sqlparse: Denial of Service via inefficient SQL parsing (CVE-2026-59893)
    * python-sqlparse: Denial of Service via quadratic CPU consumption in comment grouping (CVE-2026-71491)
    * python3.12-gitpython: Remote Code Execution via Git directory impersonation (CVE-2026-87817)
    * python3.12-sqlparse: Denial of Service via quadratic CPU consumption in SQL parsing (CVE-2026-54284)
    * python3.12-sqlparse: Denial of Service via inefficient SQL parsing (CVE-2026-59893)
    * python3.12-sqlparse: Denial of Service via quadratic CPU consumption in comment grouping     (CVE-2026-71491)
    * receptor: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages (CVE-2026-56862)
    * receptor: Go: Denial of Service via XML decoding recursion depth issue (CVE-2026-56859)
    * receptor: golang net/url: Denial of Service from quadratic complexity in path resolution     (CVE-2026-56860)
    * receptor: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal (CVE-2026-33818)
    * receptor: Go html/template: Cross-Site Scripting via pathological input (CVE-2026-56858)
    * receptor: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service (CVE-2026-56853)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    For details about this release, refer to the release notes listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 version of Atlassian Jira Service Management Data Center and Server (Jira Service Desk) running on the remote host is affected by a vulnerability as referenced in the JSDSERVER-16839 advisory.

  - js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1,     maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while     processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge     targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource     limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in     applications that parse untrusted YAML, and merge processing is enabled by default on these release lines.
    In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions     3.15.2, 4.3.2, and 5.4.1. (CVE-2026-84375)

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

The AlmaLinux 9.2 host has a package installed that is affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1792757203 advisory.

  - Grafana OSS and Grafana Enterprise did not safely resolve symbolic links when extracting plugin archives.
    A crafted plugin archive can chain relative symbolic link entries to escape the plugin installation     directory, writing arbitrary files and an executable backend binary outside that directory. The dropped     executable runs with the privileges of the Grafana server process, resulting in remote code execution.
    Plugin archives are extracted before their signature is verified, so a valid plugin signature does not     prevent the write. An operator can therefore be affected by installing a plugin that appears legitimate,     as well as by installing a plugin from an arbitrary archive using grafana-cli, the GF_INSTALL_PLUGINS     environment variable, or preinstall configuration. Grafana Enterprise is affected because it includes the     same plugin extraction code as Grafana OSS. (CVE-2026-15815)

  - Immutable.js provides many Persistent Immutable data structures. Prior to versions 3.8.3, 4.3.7, and     5.1.5, Prototype Pollution is possible in immutable via the mergeDeep(), mergeDeepWith(), merge(),     Map.toJS(), and Map.toObject() APIs. This issue has been patched in versions 3.8.3, 4.3.7, and 5.1.5.
    (CVE-2026-29063)

  - Several Grafana API endpoints, some of them unauthenticated, do not limit the size of the request body     before processing it. An attacker can send very large payloads that force excessive memory allocation,     potentially exhausting memory and causing a denial of service. (CVE-2026-33382)

  - js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 before 3.15.0 and from 4.0.0 before 4.3.0, js-     yaml can spend quadratic CPU time parsing a document whose size grows only linearly when a chain of     mappings uses merge keys where each mapping merges the previous one. This issue is fixed in versions     3.15.0 and 4.3.0. (CVE-2026-59869)

  - js-yaml is a JavaScript YAML parser and dumper. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1,     maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while     processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge     targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource     limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in     applications that parse untrusted YAML, and merge processing is enabled by default on these release lines.
    In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions     3.15.2, 4.3.2, and 5.4.1. (CVE-2026-84375)

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. From 3.0.0 until 3.15.2, 4.3.2, and 5.4.1,     maxTotalMergeKeys in lib/js-yaml/loader.js and lib/loader.js does not count empty mapping sources while     processing the merge key <<. An attacker can alias a large sequence of empty mappings into many merge     targets, causing O(N * K) processing while totalMergeKeys remains unchanged and the configured resource     limit is never reached. A relatively small YAML document can therefore cause prolonged CPU consumption in     applications that parse untrusted YAML, and merge processing is enabled by default on these release lines.
    In v3 & v4, merge is enabled by default so the severity score is higher. This issue is fixed in versions     3.15.2, 4.3.2, and 5.4.1. (CVE-2026-84375)

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

ID	Name	Product	Family	Published	Updated	Severity
462321	Echo: js-yaml: security update to 3.15.2	Tenable Self-Hosted Container Security	Echo Local Security Checks	10/2/2026	10/5/2026	high
462321	Echo: js-yaml: security update to 3.15.2	Tenable Cloud Security	Echo Local Security Checks	10/2/2026	10/5/2026	high
349536	RHEL 10 / 9 : Red Hat Ansible Automation Platform 2.6 Product Security and Bug Fix Update (Critical) (RHSA-2026:71113)	Nessus	Red Hat Local Security Checks	9/23/2026	9/25/2026	high
367873	Atlassian Jira Service Management Data Center and Server < 10.3.26 / 10.4.x < 11.3.12 (JSDSERVER-16839)	Nessus	Misc.	10/20/2026	10/20/2026	high
371221	AlmaLinux 9.2 [TuxCare] Security Update: grafana Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1792757203)	Nessus	Alma Linux Local Security Checks	10/23/2026	10/23/2026	high
342321	Linux Distros Unpatched Vulnerability : CVE-2026-84375	Nessus	Misc.	9/2/2026	11/3/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high