# RUSTSEC-2026-0244: `setlocale` and `TextDomain::init` are unsound as they access environment with no synchronization

> Unsound locale initialization in multi-threaded Rust programs can cause undefined behavior, potentially leading to code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Aug 2026

## What is RUSTSEC-2026-0244?

RUSTSEC-2026-0244 is a vulnerability in gettext-rs, published on 6 Aug 2026. 

### Official description

`setlocale` and `TextDomain::init` are unsound and may allow safe code to exhibit undefined behavior when called in a multi-threaded program.

The flaw is fixed in 0.8.0 by marking these functions `unsafe` and documenting the conditions under which they can be called safely.

## Which versions are affected by RUSTSEC-2026-0244?

1 open source package ship an affected version, including gettext-rs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gettext-rs` | crates.io | From 0.0.0-0 | 0.8.0 |

## How do I fix RUSTSEC-2026-0244?

Upgrade gettext-rs to 0.8.0 or later.

## Is RUSTSEC-2026-0244 being exploited?

There is no known exploitation of RUSTSEC-2026-0244 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0244 and fix it if it is affected.

What it is: RUSTSEC-2026-0244 is a vulnerability in gettext-rs, published on 6 Aug 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0244 in the wild and no public exploit code.

Affected packages and fixed versions:
- gettext-rs (crates.io): affected from 0.0.0-0; fixed in 0.8.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0244/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0244/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0244

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0244/
Summaries are generated and may contain mistakes; the official description above is the record.