Numeric Truncation Error Affecting rhc package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RHC-14517309
  • published18 Dec 2025
  • disclosed2 Dec 2025

Introduced: 2 Dec 2025

CVE-2025-10543  (opens in a new tab)
CWE-197  (opens in a new tab)
CWE-681  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rhc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rhc package and not the rhc package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet).

The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).

CVSS Base Scores

version 3.1