# OSV-2026-226: UNKNOWN WRITE in decode_xa2_00

> A memory corruption vulnerability in the GPS daemon allows attackers to cause a crash or potentially execute arbitrary code via crafted input.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026

## What is OSV-2026-226?

OSV-2026-226 is a memory corruption vulnerability in gpsd, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

```
Crash type: UNKNOWN WRITE
Crash state:
decode_xa2_00
tsip_parse_input
gpsd_poll
```

## Which versions are affected by OSV-2026-226?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpsd` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2026-226?

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

## Is OSV-2026-226 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2026-226 and fix it if it is affected.

What it is: OSV-2026-226 is a memory corruption vulnerability in gpsd, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2026-226 in the wild and no public exploit code.

Affected packages and fixed versions:
- gpsd (OSS-Fuzz): affected all versions; 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/OSV-2026-226/ (Markdown: https://insights.sbomify.com/OSV-2026-226/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2026-226

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