OSRM vs Aerospike

On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.

The pattern is a vendor with long-lived enterprise deployments treating branch parity as a hard requirement: every fix is labelled with the editions it affects, and Community Edition receives the same security content as Enterprise and Federal. Most of the disclosed issues sit in msgpack parsing and collection data types, which is where untrusted client input first meets the server — a concentration that suggests a focused audit of that boundary rather than scattered reports. Outside the security work, releases are small: log verbosity, lock contention on cold-start eviction, transaction object-count accuracy.

Several CVEs in this train are still marked pending assignment, so expect follow-up releases as those are published and any related parsing paths are closed out. The branch-parity discipline shown here makes it likely that whatever lands next will again ship simultaneously across all four supported lines.