The Jane OpenAPI Generator CVEs CVE-2026-63411, CVE-2026-63412, and CVE-2026-63413 affect jane-php/open-api-3 before 7.12.0. Three GitHub advisories describe one code generation weakness reached through different OpenAPI parameter fields. Teams generating PHP clients from documents an attacker can influence should track these CVEs in a vulnerability intelligence platform review. They should upgrade the generator to 7.12.0 or later and inspect generated clients.
The issue matters when an affected generator processes such a document and an application later uses the generated SDK. GitHub rates each CVE Critical at 9.3 under CVSS v4.0. The three advisories list CVSS v4.0 scores and no CVSS v3.1 score. They first appeared in July 2026; November CVE publication is an identifier update, not evidence of a new attack.
Which Jane OpenAPI Generator CVEs Share the Fix?
All three entries concern unescaped text entering generated PHPDoc comments, according to the advisories. They differ by the OpenAPI field carrying that text. The table groups them by field so teams can track one upgrade decision across three identifiers.
| CVE | OpenAPI field | Affected version | Fixed version |
|---|---|---|---|
| CVE-2026-63411 | Parameter description | Before 7.12.0 | 7.12.0 |
| CVE-2026-63412 | Query parameter name | Before 7.12.0 | 7.12.0 |
| CVE-2026-63413 | Header parameter name | Before 7.12.0 | 7.12.0 |
The generator builds PHP through an abstract syntax tree, which escapes ordinary string values. PHPDoc comment text takes a different path and is emitted raw. Special comment syntax in attacker-controlled parameter text can end the comment and place PHP code in the generated client class.
Where Does the Risk Enter the Build?
The trust boundary is the OpenAPI document supplied to the generation process. A team using reviewed specifications has a different exposure path from a pipeline accepting outside documents without review. The decisive conditions are attacker influence over the document, generation with a vulnerable release, and later use of the resulting client.
GitHub describes arbitrary PHP execution with the consuming application’s privileges when the generated client is instantiated. Its tested scenario used version 7.11.2 and PHP 8.1; that test does not narrow the published affected range. Teams accepting external API definitions can include generator workflows in their third-party risk management review.
Brandefense Blackhole recorded two dark-chat posts matching CVE-2026-63411 between August 21 and November 19, 2026. The unit is matching posts, not incidents or unique actors. Discussion alone cannot establish exploitation in a production environment.
What Should Development Teams Do Now?
Identify builds that run jane-php/open-api-3 before 7.12.0 and establish where their OpenAPI documents originate. Prioritize pipelines accepting documents outside the team’s control. The three advisories identify 7.12.0 as the fixed version.
- Find generator useRecord the Composer version and pipelines that generate clients.
- Review document originIdentify specifications supplied or changed by outside parties.
- Update and regenerateMove to 7.12.0 or later, then regenerate clients from reviewed specifications.
- Inspect deployed outputCompare generated code and deployed SDKs with approved build artifacts.
Updating the dependency alone does not replace client code already produced by an earlier run. Treat unexpected changes in generated PHP as investigation leads and preserve build records. Add the generator version and regeneration result to the vulnerability management workflow.
For ongoing builds, require a reviewed source for OpenAPI documents and inspect generated diffs before release. Record the generator version and SDK artifact used by each application. The patch management record should show which applications were rebuilt and redeployed.
Frequently Asked Questions
Which Jane version fixes the three CVEs?
GitHub's three advisories list jane-php/open-api-3 version 7.12.0 as patched. Teams should also regenerate and review clients produced by earlier builds.
Does every Jane installation face immediate code execution?
The advisory attack chain requires an attacker-influenced OpenAPI document, generation with an affected release, and use of the generated SDK.
What should teams inspect after updating Jane?
Check OpenAPI document sources and compare generated PHP and deployed SDK artifacts with approved builds.
