Skip to content
Fencer Intel
no cvss —

RUSTSEC-2026-0202 json

`let_cxx_string!` uses uninitialized value due to exception safety violations

published 4mo ago modified 4mo 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

In affected versions of this crate, `let_cxx_string!` is not exception safe. After creating the `StackString`, if `match $value` panics, the content of `StackString` is not yet initialized, while the drop implementation of `StackString` unconditionally deinitializes the content, leading to use of uninitialized value.

The soundness issue was fixed in version `1.0.195` by moving drop logics to separate drop guard after initializing the `StackString`.

Patch / fix

  • crates.io cxx 1.0.195

Is RUSTSEC-2026-0202 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
crates.io cxx
>=0.0.0-0, <1.0.195
1.0.195

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.