THE TECHNICAL RECORD
Read the proof, not the promise.
The artifact below is the same one a decision produces. Every field is inspectable, and the record underneath it is hosted by other people — we cannot write it, retract it or edit it.
PROOF EXPLORER · CVE-2026-44673
We Mathematically Prove
a Critical Vulnerability
A real, assigned vulnerability in (CVE-2026-44673, CVSS 7.5) — the YANG library behind NETCONF and sysrepo network config.
certifies your money-moving policies before an agent can act — this is that engine, shown here on a real, assigned CVE.
libyang · src/parser_lyb.c · lyb_read_string() — CWE-190 -> CWE-122
// libyang · src/parser_lyb.c · lyb_read_string() // str_len is a 32-bit length read straight from the LYB blob — attacker-controlled. L288 *str = malloc(str_len + 1); /* (str_len + 1) wraps to 0 in uint32 */ L293 lyb_read(*str, str_len * 8, in); /* str_len * 8 also wraps — no 64-bit guard */ L296 (*str)[str_len] = '\0'; /* write at [str_len] — far out of bounds */
str_len comes straight from the LYB blob, unchecked. With , (str_len + 1) wraps to 0: the parser allocates almost nothing, then writes str_len bytes into it — integer overflow to heap overflow (CWE-190 → CWE-122).
WHAT THIS PROVES — AND WHAT IT DOES NOT (declared, gate rule R3)
Proven — the 32-bit model admits an undersizing input (SAT); the 64-bit-widened model admits none (UNSAT); both fix obligations are non-vacuous — reverting the fix re-exhibits the counterexample.
Not proven here — reachability of lyb_read_string() from a given network path, and that this exact fix is the upstream libyang patch. It is a sufficient, proven-correct fix — not necessarily the one deployed.
Faithful to the Cobalt proof set (LYB-001) — reported to CESNET / libyang. View the published CVE-2026-44673 →
PUBLIC TECHNICAL RECORD
Credited in the open,
by the projects themselves
Evidence you can inspect outside our website — real upstream commits, patches and bug records that name the work.
IBM
The sarama fix commit reads: “Thanks to Dominik Blain of Cobalt AI for reporting.”
View commitGnuPG
Two libksba commits carry “Reported-by: Dominik Blain”, shipped in release 1.7.0.
View commitMozilla
Reported by Dominik Blain — recorded and resolved in Mozilla’s public bug tracker (NSS, CWE-195).
View bug recordRed Hat · OpenELA
Public libyang patches credit Dominik Blain and Cobalt AI for reporting two memory-corruption issues.
View patch recordwolfSSL
Security fixes credited to Dominik Blain in the wolfSSL 5.9.2 release notes.
View release notesVideoLAN · VLC
A vulnerability fix carrying Dominik Blain’s name is preserved in VLC’s public source tree.
View patchOFFIS · DCMTK
Three commits thank Dominik Blain for the report.
View commitpupnp · CVE-2026-41682
The pupnp advisory credits the COBALT static analyzer and Dominik Blain for the finding. CWE-195, signed-to-unsigned conversion in parse_uri().
View advisorylibmodbus
The fix commit credits Dominik Blain and Cobalt formal verification as the reporter.
View commitPUBLISHED RESEARCH