AIKIDO-2026-544238
imgref is vulnerable to Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
42
CVE Score
Medium
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
TL;DR
Two unsoundness bugs were fixed, both capable of causing Undefined Behavior: (1) ImgRef's buffer-size calculation now uses checked arithmetic, preventing integer overflow that could validate undersized buffers and cause out-of-bounds slice/iterator UB; (2) PixelsRefIter's Send impl was corrected to require T: Sync (since it yields &T), preventing a data race that constitutes UB when the iterator is sent across threads.
How do I fix this?
Upgrade the imgref library to the patch version.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range.
Package
Versions
0.0.1 - 1.12.1
Fixed in 1.12.2Background info
imgref is vulnerable to Reliance on Undefined, Unspecified, or Implementation-Defined Behavior in versions 0.0.1 - 1.12.1.
Get secure today,
quickly and for free.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPAuthorized© All Intel data is openly available and commercially licensed.