osmo-msc up to 1.15.0 src/libmsc/sgs_iface.c decode_mme_name buffer overflow

Summaryinfo

A vulnerability, which was classified as critical, was found in osmo-msc up to 1.15.0. Impacted is the function decode_mme_name of the file src/libmsc/sgs_iface.c. Such manipulation leads to buffer overflow. This vulnerability is documented as CVE-2026-104593. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in osmo-msc up to 1.15.0 and classified as critical. Affected by this issue is the function decode_mme_name of the file src/libmsc/sgs_iface.c. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is availability. CVE summarizes:

osmo-msc through 1.15.0 contains a stack-based buffer overflow in decode_mme_name() in src/libmsc/sgs_iface.c. This allows a remote attacker to cause a denial of service.

The advisory is shared for download at osmocom.org. This vulnerability is handled as CVE-2026-104593 since 10/02/2026. The exploitation is known to be easy. The attack may be launched remotely. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/26/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• osmo-msc

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15.0

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion