CVE
Tapir code injection in OpenAPI code generator
Affects tapir-openapi-codegen-core generating Scala code from an untrusted OpenAPI document before 1.13.27. Fixed in 1.13.27.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.13.27
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Generating Scala code with tapir-openapi-codegen-core from an untrusted OpenAPI document, before version 1.13.27.
Summary
Tapir, a Scala library for describing HTTP APIs, has a flaw in its OpenAPI code generator where crafted property, parameter, and tag names in an untrusted document are placed into generated Scala source without proper escaping. A local attacker who gets a user to process such a document can run arbitrary Scala code when the generated code is compiled or endpoints are assembled, without logging in.
Original description
Tapir is a Scala library for describing HTTP APIs and exposing, consuming, and documenting them using open standards. Prior to 1.13.27, tapir-openapi-codegen-core generates Scala source from untrusted OpenAPI documents by interpolating object property names, query, header, and path parameter names, and operation tags without context-appropriate validation or escaping. Crafted names or values can break out of generated identifier or string-literal contexts and inject arbitrary Scala that executes when generated code is compiled or endpoints are assembled. This is a code-generation and build-time issue and does not make a running tapir server directly exploitable. This issue is fixed in version 1.13.27.
Who should check
Anyone generating Scala code with tapir-openapi-codegen-core (sbt plugin or CLI) from OpenAPI documents they did not write, such as third-party specs.
“The OpenAPI code generator (tapir-openapi-codegen-core) builds Scala source by string templating”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch0/5No signal
What would change the score
- Would score about 63 if added to CISA KEV
- Would score about 58 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Generating Scala code with tapir-openapi-codegen-core from an untrusted OpenAPI document, before version 1.13.27.Upgrade to a fixed version: 1.13.27.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-76090 (Tapir: Construction/decode RCE via property name -> raw case-class field (tapir-openapi-codegen)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-76090 (entry last updated 2026-11-18):
Affected:
- softwaremill tapir: fixed in 1.13.27
Fixed versions: 1.13.27.
Conditions (all must be true for the bug to be hit):
- Generating Scala code with tapir-openapi-codegen-core from an untrusted OpenAPI document, before version 1.13.27. (source: https://github.com/softwaremill/tapir/security/advisories/GHSA-gpcc-36pq-8qxr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-76090 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-76090 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/softwaremill/tapir/security/advisories/GHSA-gpcc-36pq-8qxr
- https://github.com/softwaremill/tapir/pull/5395
- https://github.com/softwaremill/tapir/commit/e015939b78df2de0fa3d3b8ed02961425e02145e
- https://github.com/softwaremill/tapir/releases/tag/v1.13.27
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-76090
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-76090"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- softwaremill tapir
fixed in 1.13.27
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · softwaremill/tapir · Advisory GHSA-gpcc-36pq-8qxr |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-76090 |
| Record | NVD · CVE-2026-76090 |
| Other links 3 | |
| Repository | GitHub · softwaremill/tapir · Pull request #5395 |
| Repository | GitHub · softwaremill/tapir · Commit e015939b |
| Repository | GitHub · softwaremill/tapir · Release v1.13.27 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76090
Is CVE-2026-76090 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The OpenAPI code generator builds Scala source by string templating, and a crafted property name can inject arbitrary Scala code. That injected code runs at build time when the generated code is compiled or endpoints are assembled.Source: github.com
Which versions are affected by CVE-2026-76090?
tapir: before 1.13.27.Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are tapir-openapi-codegen-core before 1.13.27, when it generates Scala code from an untrusted OpenAPI document. To check, look at the tapir-openapi-codegen-core version in the build dependencies.Source: github.com
How do I fix CVE-2026-76090?
Upgrade tapir-openapi-codegen-core to 1.13.27 or later, which contains the fix.Source: github.com