# CVE-2026-2274: Arbitrary File Read and SSRF in Google AppSheet

> Authenticated attackers can read local files and access internal networks via SSRF in Google AppSheet, requiring patched server software.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/U:Clear`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2026
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-f6rv-5qch-vwvw

## What is CVE-2026-2274?

CVE-2026-2274 is a high-severity server-side request forgery vulnerability in AppSheet Web (Main Server), published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SSRF and Arbitrary File Read vulnerability in AppSheet Core in Google AppSheet prior to 2025-11-23 allows an authenticated remote attacker to read sensitive local files and access internal network resources via crafted requests to the production cluster.

This vulnerability was patched and no customer action is needed.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-2274 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2274 is a high-severity server-side request forgery vulnerability in AppSheet Web (Main Server), published on 19 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2274 in the wild and no public exploit code.

Affected product: AppSheet Web (Main Server). 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-2274/ (Markdown: https://insights.sbomify.com/CVE-2026-2274/index.md)
```

## Sources

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

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