CVE-2026-13481 Vulnerability Analysis & Exploit Details

CVE-2026-13481
Vulnerability Scoring

5.4
/10
Significant Risk

Security assessments indicate that CVE-2026-13481 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Adjacent_network
    Attack Vector Under Analysis
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-13481 Details

Status: Analyzed

Last updated: 🕥 31 Aug 2026, 22:46 UTC
Originally published on: 🕒 26 Aug 2026, 15:16 UTC

Time between publication and last update: 5 days

CVSS Release: version 3

CVSS3 Source

vulnerabilities@zephyrproject.org

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVE-2026-13481 Vulnerability Summary

CVE-2026-13481: The IEEE 1588 PTP management-message parser in subsys/net/lib/ptp/tlv.c mishandles the PTP_MGMT_TIME management id. In tlv_mgmt_post_recv(), the PTP_MGMT_TIME case casts mgmt_tlv->data to a 10-byte struct ptp_timestamp and reads it (then byte-swaps and writes it back) without first checking that the TLV data field is at least sizeof(struct ptp_timestamp). Every sibling management id in the same switch validates its length first; PTP_MGMT_TIME was the only case lacking that check. The length passed in is the management data size (tlv->length - 2), and the upstream guard in ptp_tlv_post_recv() only requires tlv->length > 2, while msg_tlv_post_recv() validates only that the TLV fits within the received byte count, not a per-id minimum. A peer on the local PTP segment can therefore send a PTP_MSG_MANAGEMENT message carrying a short PTP_MGMT_TIME TLV (data as small as 2 bytes), causing the parser to read and write 8 bytes beyond the validated data. The message type and TLV contents are taken straight off the wire, so the path is reachable by any adjacent attacker when CONFIG_PTP is enabled. The over-read and write-back stay within the struct ptp_msg allocation (mgmt_tlv->data lives in the leading mtu[NET_ETH_MTU] union member, so data + 10 lands at most a few bytes past mtu[], inside the same object), so this is an out-of-bounds read of adjacent in-object memory plus a bounded in-place corruption of the message's parsed timestamp, not past-allocation memory corruption. Impact is limited to minor information exposure of adjacent bytes and corruption of the device's parsed management TIME value; there is no crash on the access and no reachable reference-count corruption. The fix adds if (length < sizeof(struct ptp_timestamp)) { return -EBADMSG; } before the cast, matching the other management-id cases and fully closing the receive-path defect.

Assessing the Risk of CVE-2026-13481

Access Complexity Graph

The exploitability of CVE-2026-13481 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-13481

With low attack complexity and no required privileges, CVE-2026-13481 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-13481, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-13481, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-13481 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: Low
    Exploiting CVE-2026-13481 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2026-13481 does not impact system availability.

CVE-2026-13481 References

External References

CWE Common Weakness Enumeration

CWE-125

CAPEC Common Attack Pattern Enumeration and Classification

  • Overread Buffers CAPEC-540 An adversary attacks a target by providing input that causes an application to read beyond the boundary of a defined buffer. This typically occurs when a value influencing where to start or stop reading is set to reflect positions outside of the valid memory location of the buffer. This type of attack may result in exposure of sensitive information, a system crash, or arbitrary code execution.

Vulnerable Configurations

  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.1:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.1:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.2:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.2:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:3.7.2:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:3.7.2:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.0.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.1.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.3.1:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:-:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc2:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.0:rc3:*:*:*:*:*:*
  • cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*
    cpe:2.3:o:zephyrproject:zephyr:4.4.1:-:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-13481: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97318 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not properly validate a giveaway's parent page URL before saving it...
  • CVE-2026-97317 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not remove the reCAPTCHA secret key from the giveaway settings it e...
  • CVE-2026-94298 – The BuildKit WordPress plugin before 1.0.29 does not properly sanitise and escape data submitted by contributor-level users before storing it and ...
  • CVE-2026-92820 – The Ninja Forms - File Uploads plugin for WordPress is vulnerable to arbitrary file operations in all versions up to, and including, 3.3.34 via the...
  • CVE-2026-92174 – The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.73.2 via the 'them...