# CVE-2026-45325: Gestor de Oferta: Prototype pollution in @tmlmobilidade/utils setValueAtPath

> Prototype pollution in the setValueAtPath function allows attackers to inject properties into Object.prototype, potentially leading to code execution or privilege escalation.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** AZL-110400, AZL-110403, GHSA-cmxg-94mg-jq94

## What is CVE-2026-45325?

CVE-2026-45325 is a high-severity code injection vulnerability in tmlmobilidade go, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gestor de Oferta is a web application for managing mobility service offerings. Prior to 20260509.0340.15, @tmlmobilidade/utils has a prototype pollution vulnerability in setValueAtPath() in packages/utils/src/generic/value-at-path.ts because unsafe path segments are not blocked. This issue is fixed in version 20260509.0340.15.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2026-45325?

2 open source packages ship an affected version, including @tmlmobilidade/utils.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@tmlmobilidade/utils` | npm | All versions | 20260509.0340.15 |
| `@tmlmobilidade/utils` | npm | All versions | 20260509.0340.15 |

## How do I fix CVE-2026-45325?

Upgrade @tmlmobilidade/utils to 20260509.0340.15 or later.

## Is CVE-2026-45325 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-45325 and fix it if it is affected.

What it is: CVE-2026-45325 is a high-severity code injection vulnerability in tmlmobilidade go, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-45325 in the wild and no public exploit code.

Affected packages and fixed versions:
- @tmlmobilidade/utils (npm): affected all versions; fixed in 20260509.0340.15
- @tmlmobilidade/utils (npm): affected all versions; fixed in 20260509.0340.15

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

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-45325
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-45325
- OSV: https://osv.dev/vulnerability/CVE-2026-45325

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