Vulnerability · OSV-2026-655
Heap-buffer-overflow in lj_record_idx
Published Apr 30, 2026 · catalog updated Oct 18, 2026 · Heap-buffer-overflow in lj_record_idx
Open the advisory
Exploitation likelihood is not on this record for OSV-2026-655. A missing EPSS score is not a low risk. Compare Heap-buffer-overflow in lj_record_idx with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Heap-buffer-overflow in lj_record_idx).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- OSS-Fuzz tarantool
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=507646002
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- OSS-Fuzz tarantoolfrom 41846ade3585 (github.com/tarantool/tarantool)
How to fix OSV-2026-655
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for OSV-2026-655. A missing EPSS score is not a low risk. Compare Heap-buffer-overflow in lj_record_idx with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with from 41846ade3585 (github.com/tarantool/tarantool). Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Apr 30, 2026 · OpenSSF OSV / OSV Scanner
Detected
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=507646002
Oct 17, 2026 · OpenSSF OSV / OSV Scanner
Updated
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=507646002
Oct 18, 2026 · OpenSSF OSV / OSV Scanner
Updated
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=507646002
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryOSV-2026-655
Heap-buffer-overflow in lj_record_idx
osv.dev
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.