Vulnerability in @tmlmobilidade/utils (CVE-2026-45325)
Summary
Vulnerability in @tmlmobilidade/utils (CVE-2026-45325). Data can be tampered with by attackers. Mitigation: upgrade to 20260509.0340.15 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45325 has been found in @tmlmobilidade/utils.
Data can be tampered with by attackers. CVSS score: 8.2/10.
What to do: upgrade @tmlmobilidade/utils to 20260509.0340.15 or later.
If unsure, ask your IT team or search "@tmlmobilidade/utils CVE-2026-45325" on the vendor's site.
CVE-2026-45325 (@tmlmobilidade/utils) — CWE-1321 / CVSS v3 8.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 20260509.0340.15 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in @tmlmobilidade/utils.
Check the vendor advisory for the affected versions of @tmlmobilidade/utils.
Severity: High (CVSS 8.2/10). Data can be tampered with by attackers.
Update to 20260509.0340.15.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@tmlmobilidade/utils' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@tmlmobilidade/utils' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@tmlmobilidade/utilsを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @tmlmobilidade/utils to 20260509.0340.15ステージング環境で 20260509.0340.15 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com