Its advisory says an attacker-influenced OpenAPI parameter description can escape a generated PHPDoc comment. If an application then instantiates the generated client, attacker-controlled PHP can run with that application's privileges.Two related identifiers cover the same PHPDoc boundary in different inputs. CVE-2026-63412 concerns a query parameter name, while CVE-2026-63413 concerns a header parameter name. All three affect jane-php/open-api-3 before 7.12.0 and share the 7.12.0 fix.
What it allows
How Does CVE-2026-63411 Become Code Execution?
Jane generates PHP clients from OpenAPI documents. The advisories explain that its parser escapes PHP string literals, but inserts some parameter text into generated method PHPDoc without neutralizing comment syntax. A malicious description can close the comment early and leave attacker-controlled PHP in the generated class body.
The reported demonstration adds a constructor that runs when the generated client is instantiated. The attack therefore needs two steps: generate a client from an attacker-influenced document, then use that generated client. Merely viewing an OpenAPI document is not the execution condition described by the advisories.
CVE-2026-63412 applies the same boundary failure to query parameter names. CVE-2026-63413 applies it to header parameter names. These are separate input paths with separate identifiers, not three independent incidents.
The advisories include researcher reproduction material and say the behavior was verified with Jane 7.11.2 and PHP 8.1. That is a demonstration of exploitability, not evidence of attacks against deployed applications. Brandefense Blackhole counted two dark-chat posts mentioning CVE-2026-63411, two mentioning CVE-2026-63412, and three mentioning CVE-2026-63413 from 21 August through 19 November 2026. Each count measures posts mentioning one identifier; overlapping posts are possible, and the counts do not prove exploitation.
Teams can use a software supply chain risk review to trace which generated SDKs entered applications. For related product context, see the Vulnerability Intelligence platform. Neither inventory nor discussion data alone confirms that a generated client contains injected code.
Who is affected
Which Jane OpenAPI Versions Are Affected by CVE-2026-63411?
The three advisories identify the Composer package jane-php/open-api-3 before version 7.12.0 as affected. Version 7.12.0 is the patched release for all three identifiers. The exposure requires generation from an attacker-influenced OpenAPI document and later instantiation of the generated client.
Check the resolved Composer version in each build environment, not only the declared constraint. Then trace the origin and approval of OpenAPI documents used to regenerate clients. A generated SDK built earlier from an untrusted document merits review even if the generator dependency has since been upgraded.
The advisories provide one upper version boundary and no branch-specific release table. Verify the installed package and the provenance of generated artifacts manually. Record this in the patch management process so a later regeneration does not restore unsafe output.
Timeline
- 2026-07-09
The three JanePHP security advisories show an initial publication date of 9 July 2026.
- 2026-11-18
NVD published the CVE-2026-63411, CVE-2026-63412 and CVE-2026-63413 records.
- 2026-11-19
GitHub published the three entries to its reviewed Advisory Database.
What to do
-
Inventory Jane generator use
Find builds using jane-php/open-api-3 and record the resolved Composer version. Identify the OpenAPI documents and generated client artifacts in each pipeline.
-
Upgrade and regenerate trusted clients
Upgrade jane-php/open-api-3 to 7.12.0 or later. Regenerate clients from approved OpenAPI documents, then rebuild and redeploy consuming applications.
-
Verify the running version and artifact
Confirm the build resolves jane-php/open-api-3 at 7.12.0 or later. Check that the deployed SDK came from the patched build and approved document.
-
Restrict untrusted specifications
Require review of externally supplied OpenAPI documents before code generation. Treat a change to parameter descriptions and names as a code generation input change.
-
Review earlier generated clients
Inspect generated client code and build history for unexpected class members or changes after untrusted specifications entered the pipeline. This is a defensive review suggestion, not a vendor detection signature.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-63411 in Brandefense Atlas
The Atlas record of CVE-2026-63411: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What distinguishes CVE-2026-63411 from CVE-2026-63412 and CVE-2026-63413?
The first uses a parameter description, the second a query parameter name, and the third a header parameter name. All three affect generated PHPDoc.
Does reading an OpenAPI document trigger the flaw?
The advisories require generating a client from an attacker-influenced document and then using the generated SDK. The reported demonstration runs code when the client is instantiated.
Which version fixes all three Jane OpenAPI issues?
The GitHub advisories list jane-php/open-api-3 version 7.12.0 as patched for CVE-2026-63411, CVE-2026-63412 and CVE-2026-63413.
Does a patched generator repair an older generated SDK?
Upgrade the generator and regenerate the client from a trusted specification. Verify that the deployed SDK came from the patched build.
Sources
- Jane Parameter Description PHPDoc InjectionJanePHP via GitHub Advisory Database
- Jane Query Parameter Name PHPDoc InjectionJanePHP via GitHub Advisory Database
- Jane Header Parameter Name PHPDoc InjectionJanePHP via GitHub Advisory Database