Skip to main content
Mallory
← Back to News
proof-of-concept-releaseopen-source-dependency-vulnerabilityendpoint-software-vulnerability

Out-of-Bounds Read in traceroute MPLS Extension Parsing

Patch & Detection Intelligence · 5 sources · Updated 5mo ago · First seen Apr 29, 2026

Out-of-Bounds Read in traceroute MPLS Extension Parsing

A remotely triggerable out-of-bounds read vulnerability was disclosed in traceroute 2.1.2, affecting MPLS extension parsing when the tool is run with -e. Researcher Mohamed Aziz Rahmouni reported that in traceroute/traceroute.c, the packet buffer pointer is advanced past the IP header after recvmsg(), but the packet length variable is not reduced before handle_extensions() is called. That mismatch can cause the parser to read past the actual received packet boundary and into uninitialized stack memory in buf[1280] when processing a crafted ICMP Time Exceeded response carrying MPLS extensions from an on-path network device.

The researcher said the flaw was identified through manual code review and dynamic fuzzing, confirmed with a working proof of concept, and could be corrected with a one-line fix that subtracts the header length from the packet length after advancing the buffer pointer. traceroute maintainer Dmitry Butskoy acknowledged the report on the oss-sec mailing list and said he would review it within hours, while the disclosure followed a 90-day responsible disclosure timeline with public technical details planned unless a patch is released sooner.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

3 events · Apr 28, 2026 – Apr 29, 2026
  1. Apr 29, 20267mo ago

    Maintainer and oss-sec participants dispute traceroute OOB read claim

    In follow-up oss-sec discussion, Dmitry Butskoy said the cited code had long included the key "n -= hlen;" logic, including in current traceroute releases, and Solar Designer questioned why the report targeted 2.1.2. The thread indicated the reported MPLS parsing out-of-bounds read was likely based on faulty analysis rather than a confirmed vulnerability.

    oss-sec: Re: [SECURITY] Out-of-Bounds Read in MPLS Extension Parsing - traceroute 2.1.2
  2. Apr 29, 20267mo ago

    Traceroute maintainer acknowledges report and says review is underway

    Dmitry Butskoy replied on oss-sec acknowledging the vulnerability report and said he would review it within a few hours. The follow-up reiterated the planned 90-day disclosure timeline, with public disclosure targeted for 2026-07-27 unless a patch is released sooner.

  3. Apr 28, 20267mo ago

    Researcher publicly discloses traceroute 2.1.2 MPLS parsing OOB read

    On the oss-sec mailing list, Mohamed Aziz Rahmouni disclosed an out-of-bounds read vulnerability in traceroute 2.1.2 affecting MPLS extension parsing. The report said the flaw is remotely triggerable by an on-path device via a crafted ICMP Time Exceeded response to traceroute -e, included a confirmed proof of concept, and proposed a one-line fix.

Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.