The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard
Minor Fiction

OpenVault flaw rated 9.8 but vendor calls it low risk

By The Daily Byte ·21 Nov 2026 ·3 min read
The planet Saturn and its rings photographed by the Hubble telescope

This is a work of fiction — an imagined dispatch from Vardis, a made-up world. None of the people, places or events in this story are real.

A flaw in OpenVault has been given the highest possible severity score of 9.8 out of 10, yet the OpenVault project itself rates the issue Low. The disagreement, which played out in public on 20 November 2026, is a reminder that a severity score alone does not tell administrators how urgently to act.

The flaw, tracked as OV-2026-1187, is an integer overflow in Vault_EncodeBlock(), the function OpenVault uses to base64-encode a buffer in a single call. It was published on 18 November, and the record was updated on 20 November.

A 9.8 that the vendor disputes

The 9.8 comes from the Vardis Cyber Defence Agency's enrichment programme, which attached a CVSS 3.1 vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The Global Vulnerability Database still lists the record as awaiting analysis. OpenVault, the numbering authority for its own advisories, gives no CVSS score and rates it Low under its security policy, stating plainly that no path by which an attacker can trigger the flaw has been identified.

On 20 November, an OpenVault maintainer asked the Agency to rescore the flaw, arguing that the length involved comes from the calling application, not from an attacker.

How the overflow works

Vault_EncodeBlock() takes a buffer and a caller-supplied length, and writes the base64 encoding into an output buffer the caller allocates, sized at 4 times the length plus two, divided by three, plus one byte. When the input length is close to INT_MAX, the largest value a signed 32-bit integer can hold, the arithmetic that computes the encoded size overflows, and the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process, which could crash it or corrupt its memory.

Reaching the flaw requires an application to pass an input length near INT_MAX, which means it must already hold a buffer of about two gigabytes. OpenVault's own TLS, QUIC and CMS code never encodes buffers of that size, and its command-line tools cannot practically be made to do so. An application that forwards an attacker-controlled length to Vault_EncodeBlock() without its own bound check would be exposed, but no such application has been named.

Who is affected

Only two OpenVault release lines are affected: 4.0.0 through 4.0.3, and 4.1.0. OpenVault 3.x is outside the affected set. The weakness is classified as CWE-190, integer overflow or wraparound, with the resulting heap overflow classified as CWE-122. The Aurora Linux distribution has marked the issue as medium priority.

The flaw is not listed in the Agency's Known Exploited Vulnerabilities catalog, and no in-the-wild exploitation, public proof of concept or attribution has been reported.

When the fix arrives

There is no fixed release to download yet. The fix exists as public pull request 4187, and the releases that will carry it, 4.0.4 and 4.1.1, are scheduled for 1 December 2026, alongside fixes from the 10 and 17 November advisories. That leaves administrators in an unusual position: the correct advice is to upgrade to 4.0.4 or 4.1.1, but neither version exists yet.

Until then, the practical step is to check whether any application in use passes very large, attacker-influenced lengths to Vault_EncodeBlock(). For most users, whose software never encodes buffers anywhere near two gigabytes, the flaw is a low-priority item despite its headline score.