# CVE-2026-12535: Formatter Field - Critical - PHP object injection - SA-CONTRIB-2026-048

> An attacker can exploit PHP object injection in the Drupal Formatter Field module to potentially execute arbitrary code.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** DRUPAL-CONTRIB-2026-048, GHSA-qc2r-2xxp-m58x

## What is CVE-2026-12535?

CVE-2026-12535 is a critical unsafe deserialization vulnerability in Drupal Formatter Field, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Formatter Field allows Object Injection. This issue affects Formatter Field versions: from 0.0.0 to 2.0.0.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/formatter_field` | Packagist:https://packages.drupal.org/8 | All versions | 2.0.0 |

Products: Zroger Formatter Field.

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

Upgrade to a fixed version.

## Is CVE-2026-12535 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12535 is a critical unsafe deserialization vulnerability in Drupal Formatter Field, published on 10 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-12535 in the wild and no public exploit code.

Affected product: Drupal Formatter Field. 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-12535/ (Markdown: https://insights.sbomify.com/CVE-2026-12535/index.md)
```

## Sources

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

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