python-engineio is a Python implementation of the Engine.IO realtime client and server. Prior to version 4.13.2, an attacker can cause the creation of unnecessary background threads in the python-engineio server by exploiting the heartbeat mechanism, which launches a thread when a new connection is received, and when the client sends a PONG packet. This issue primarily affects synchronous servers. Asynchronous servers allocate background tasks instead of physical threads, which are lightweight and less likely to cause denial of service. However, the fix that was implemented was also applied to the asynchronous case. Version 4.13.2 addresses this issue as follows: The initial background thread (or async task( for heartbeat management is only launched if a client passes authentication in the `connect` handler; and the server now ensures that there is only one background heatbeat thread (or async task) per client at a given point in time. Out of sequence PONG packets are now discarded when an active heartbeat thread is already running.

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

  - python-engineio is a Python implementation of the Engine.IO realtime client and server. Prior to version     4.13.2, an attacker can cause the creation of unnecessary background threads in the python-engineio server     by exploiting the heartbeat mechanism, which launches a thread when a new connection is received, and when     the client sends a PONG packet. This issue primarily affects synchronous servers. Asynchronous servers     allocate background tasks instead of physical threads, which are lightweight and less likely to cause     denial of service. However, the fix that was implemented was also applied to the asynchronous case.
    Version 4.13.2 addresses this issue as follows: The initial background thread (or async task( for     heartbeat management is only launched if a client passes authentication in the `connect` handler; and the     server now ensures that there is only one background heatbeat thread (or async task) per client at a given     point in time. Out of sequence PONG packets are now discarded when an active heartbeat thread is already     running. (CVE-2026-48802)

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

The remote SUSE Linux SLED15 / SLED_SAP15 / SLES15 / SLES_SAP15 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2026:3085-1 advisory.

    - CVE-2026-48802: remote user can cause the creation of unnecessary background       threads in the server through the heartbeat mechanism and cause a DoS       (bsc#1269544).
    - CVE-2026-48809: size of incoming messages is not checked before they are loaded       into memory and allows remote users to cause a DoS via excessive memory allocation       (bsc#1269545).

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 remote openSUSE 16 host has a package installed that is affected by multiple vulnerabilities as referenced in the openSUSE-SU-2026:21182-1 advisory.

    Changes in python-python-engineio:

    - CVE-2026-48802: remote user can cause the creation of unnecessary       background threads in the server through the heartbeat mechanism       and cause a DoS (bsc#1269544)
    - CVE-2026-48809: size of incoming messages is not checked before       they are loaded into memory and allows remote users to cause a DoS       via excessive memory allocation (bsc#1269545)

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.

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

  - python-engineio is a Python implementation of the Engine.IO realtime client and server. Prior to version
    4.13.2, an attacker can cause the creation of unnecessary background threads in the python-engineio server
    by exploiting the heartbeat mechanism, which launches a thread when a new connection is received, and when
    the client sends a PONG packet. This issue primarily affects synchronous servers. Asynchronous servers
    allocate background tasks instead of physical threads, which are lightweight and less likely to cause
    denial of service. However, the fix that was implemented was also applied to the asynchronous case.
    Version 4.13.2 addresses this issue as follows: The initial background thread (or async task( for
    heartbeat management is only launched if a client passes authentication in the `connect` handler; and the
    server now ensures that there is only one background heatbeat thread (or async task) per client at a given
    point in time. Out of sequence PONG packets are now discarded when an active heartbeat thread is already
    running. (CVE-2026-48802)

ID	Name	Product	Family	Type	Severity
335307	Linux Distros Unpatched Vulnerability : CVE-2026-48802	Nessus	Misc.	Local	high
327736	SUSE SLED15 / SLES15 Security Update : python-python-engineio (SUSE-SU-2026:3085-1)	Nessus	SuSE Local Security Checks	Local	high
324887	openSUSE 16 Security Update : python-python-engineio (openSUSE-SU-2026:21182-1)	Nessus	SuSE Local Security Checks	Local	high
444077	SCA: security update for python-engineio (GHSA-cgwc-pv48-fhj5)	Tenable Cloud Security	SCA Checks	Local	high
444077	SCA: security update for python-engineio (GHSA-cgwc-pv48-fhj5)	Tenable Self-Hosted Container Security	SCA Checks	Local	high

Detections

Analytics

CVE-2026-48802

high

Tenable Plugins

high

high

high

high

high