# CVE-2026-30290: Path traversal in n/a

> Attackers can overwrite critical files via the import process in InTouch Contacts & Caller ID APP, enabling code execution or data exposure.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 31 Mar 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-7gqr-hjwm-vh6c

## What is CVE-2026-30290?

CVE-2026-30290 is a high-severity path traversal vulnerability in n/a, published on 31 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An arbitrary file overwrite vulnerability in InTouch Contacts & Caller ID APP v6.38.1 allows attackers to overwrite critical internal files via the file import process, leading to arbitrary code execution or information exposure.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Intouchapp Intouch Contacts \& Caller Id.

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

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

## Is CVE-2026-30290 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30290 is a high-severity path traversal vulnerability in n/a, published on 31 Mar 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 CVE-2026-30290 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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