# CVE-2026-27449: Umbraco.Engage.Forms Allows Unauthorized Access to Multiple API Endpoints

> Unauthenticated attackers can access sensitive data via exposed API endpoints by enumerating identifiers, requiring an upgrade to patched versions.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-86vq-ccwf-rm62

## What is CVE-2026-27449?

CVE-2026-27449 is a high-severity missing authorization vulnerability in Umbraco.Engage.Forms, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Umbraco Engage is a business intelligence platform. A vulnerability has been identified in Umbraco Engage prior to versions 16.2.1 and 17.1.1 where certain API endpoints are exposed without enforcing authentication or authorization checks. The affected endpoints can be accessed directly over the network without requiring a valid session or user credentials. By supplying a user-controlled identifier parameter (e.g., ?id=), an attacker can retrieve sensitive data associated with arbitrary records. Because no access control validation is performed, the endpoints are vulnerable to enumeration attacks, allowing attackers to iterate over identifiers and extract data at scale. An unauthenticated attacker can retrieve sensitive Engage-related data by directly querying the affected API endpoints. The vulnerability allows arbitrary record access through predictable or enumerable identifiers. The confidentiality impact is considered high. No direct integrity or availability impact has been identified. The scope of exposed data depends on the deployment but may include analytics data, tracking data, customer-related information, or other Engage-managed content. The vulnerability affects both v16 and v17. Patches have already been released. Users are advised to update to 16.2.1 or 17.1.1. No known workarounds are available.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control)

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

4 open source packages ship an affected version, including Umbraco.Engage.Forms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Umbraco.Engage.Forms` | NuGet | From 16.0.0 | 16.2.1 |
| `Umbraco.Engage.Forms` | NuGet | From 16.0.0 | 16.2.1 |
| `Umbraco.Engage.Forms` | NuGet | From 17.0.0 | 17.1.1 |
| `Umbraco.Engage.Forms` | NuGet | From 17.0.0 | 17.1.1 |

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

Upgrade Umbraco.Engage.Forms to a fixed version for your release line: 16.2.1 or 17.1.1.

## Is CVE-2026-27449 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27449 is a high-severity missing authorization vulnerability in Umbraco.Engage.Forms, published on 26 Feb 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-27449 in the wild and no public exploit code.

Affected packages and fixed versions:
- Umbraco.Engage.Forms (NuGet): affected from 16.0.0; fixed in 16.2.1
- Umbraco.Engage.Forms (NuGet): affected from 16.0.0; fixed in 16.2.1
- Umbraco.Engage.Forms (NuGet): affected from 17.0.0; fixed in 17.1.1
- Umbraco.Engage.Forms (NuGet): affected from 17.0.0; fixed in 17.1.1

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

## Sources

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

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