# RUSTSEC-2026-0197: `Matrix{2,3,4}::swap_columns` can trigger undefined behavior for identical indices

> Calling swap_columns with identical indices causes undefined behavior via aliasing violations, potentially leading to crashes or 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:** No
- **Published:** 11 Mar 2026

## What is RUSTSEC-2026-0197?

RUSTSEC-2026-0197 is a memory corruption vulnerability in cgmath, published on 11 Mar 2026. 

### Official description

The `Matrix2::swap_columns`, `Matrix3::swap_columns`, and `Matrix4::swap_columns`
implementations call `ptr::swap(&mut self[a], &mut self[b])`.

When `a == b`, these safe APIs create two mutable references to the same matrix
column and pass them to `ptr::swap`. This violates Rust's aliasing rules and can
trigger undefined behavior. The issue can be reproduced from safe Rust by calling
`swap_columns` with identical column indices, for example `m.swap_columns(0, 0)`.

A minimal fix is to return early when the two column indices are equal before
calling `ptr::swap`.

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

1 open source package ship an affected version, including cgmath.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cgmath` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for RUSTSEC-2026-0197 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0197 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0197 is a memory corruption vulnerability in cgmath, published on 11 Mar 2026. 
Exploitation: There is no known exploitation of RUSTSEC-2026-0197 in the wild and no public exploit code.

Affected packages and fixed versions:
- cgmath (crates.io): affected from 0.0.0-0; no fix listed

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-0197/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0197/index.md)
```

## Sources

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

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