Skip to content
Fencer Intel
no cvss —

OSV-2026-1070 json

UNKNOWN READ in bytes1_char_at

published 3mo ago modified 3mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=538179114

``` Crash type: UNKNOWN READ Crash state: bytes1_char_at unicode_word_left unicode_at_boundary ```

Is OSV-2026-1070 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
pypi mrab-regex
10 listed versions
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.