CyberSecBulletin

Use of Incorrect Byte Ordering

CWE-198

The product receives input from an upstream component, but it does not account for byte ordering (e.g. big-endian and little-endian) when processing the input, causing an incorrect number or value to be used.

We track 2 vulnerabilities of this type. 100% are rated high or critical, and the average CVSS score is 7.5.

Latest Use of Incorrect Byte Ordering vulnerabilities

  • 7.5 High severity

    Linux: Use of Incorrect Byte Ordering

    CVE-2026-46306Linux

    In the Linux kernel, the following vulnerability has been resolved: flow_dissector: do not dissect PPPoE PFC frames RFC 2516 Section 7 states that Protocol Field Compression (PFC) is NOT RECOMMENDED for PPPoE. In practice, pppd does not support negotiating PFC

  • 7.5 High severity

    Junos OS: Use of Incorrect Byte Ordering

    CVE-2025-52980Juniper Networks

    A Use of Incorrect Byte Ordering vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS on SRX300 Series allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). When a BGP update is received over an establ