Jane PHP remote code execution in OpenAPI 3 generator
Affects jane-php/open-api-3 before 7.12.0 when a client is generated from an attacker-influenced OpenAPI document and the generated SDK is used. Fixed in 7.12.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.12.0
- Who is exposed
- Not reported
Summary
The janephp "Jane" PHP libraries, specifically the open-api-3 generator, can be exploited remotely and without logging in to run arbitrary PHP code with the privileges of the consuming application. An attacker supplies an OpenAPI document with a crafted parameter description that the generator copies unescaped into client code, so the injected PHP runs when the generated client is instantiated.
Written by a model
Original description
Jane is a set of PHP libraries that generates models and API clients from JSON Schema and OpenAPI specifications. Prior to 7.12.0, the Jane open-api-3 generator emits an OpenAPI parameter description verbatim in generated Client/Endpoint method docblocks. A parameter description containing a PHPDoc closing delimiter can terminate the comment early and place attacker-controlled PHP in class-body position, including an __construct method that runs when the generated Client is instantiated. Exploitation requires generating a client from an attacker-influenced OpenAPI document and then using the generated SDK, and can execute arbitrary PHP with the consuming application's privileges. This issue is fixed in version 7.12.0.
Who should check
Teams running jane-php/open-api-3 before 7.12.0 that generate PHP API clients or models from OpenAPI or JSON Schema documents they do not fully control
“Affected package: jane-php/open-api-3 (and sibling generators)”
What to do
Upgrade to a fixed version: 7.12.0.
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-63411 (Jane: Instantiation RCE via parameter description -> raw PHPDoc */ breakout (jane-php/open-api-3)), 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-63411 (entry last updated 2026-11-18):
Affected:
- janephp janephp: fixed in 7.12.0
Fixed versions: 7.12.0.
Conditions (all must be true for the bug to be hit):
- Uses jane-php/open-api-3 before 7.12.0 (verified on 7.11.2) (source: https://github.com/janephp/janephp/security/advisories/GHSA-xwcw-j52r-34x4)
- A client is generated from an attacker-influenced OpenAPI document and the generated SDK is then used (source: https://github.com/janephp/janephp/security/advisories/GHSA-xwcw-j52r-34x4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63411 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63411 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/janephp/janephp/security/advisories/GHSA-xwcw-j52r-34x4
- https://github.com/janephp/janephp/pull/960
- https://github.com/janephp/janephp/commit/0ea379deab5689475d62653b408de62ad3611c7a
- https://github.com/janephp/janephp/releases/tag/v7.12.0
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-63411
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-63411"}.Affected versions
- janephp janephpfixed in 7.12.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now1 day
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.47%
- Posted on X by cve.now Nov 19
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · janephp/janephp · Advisory GHSA-xwcw-j52r-34x4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-63411 |
| Record | NVD · CVE-2026-63411 |
| Other links 3 | |
| Repository | GitHub · janephp/janephp · Pull request #960 |
| Repository | GitHub · janephp/janephp · Commit 0ea379de |
| Repository | GitHub · janephp/janephp · Release v7.12.0 |
Questions about CVE-2026-63411
Is CVE-2026-63411 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?
Attacker-supplied PHP runs with the consuming application's privileges when the generated client is instantiated, giving remote code execution. The flaw is a parameter description that breaks out of a raw PHPDoc comment.
Source: github.com
Which versions are affected by CVE-2026-63411?
janephp: before 7.12.0.
Source: cve.now feed data
Am I affected, and how do I check?
Versions before 7.12.0 are affected; the issue was verified on 7.11.2 with PHP 8.1. The vulnerable setup is generating a client from an attacker-influenced OpenAPI document and using the generated SDK. To check a installed version, run composer show jane-php/open-api-3 or inspect composer.lock.
Source: github.com
How do I fix CVE-2026-63411?
Upgrade jane-php/open-api-3 to 7.12.0 or later.
Source: github.com
Related
- CVE-2026-63412Jane: Instantiation RCE via query parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
- CVE-2026-63413Jane: Instantiation RCE via header parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
- CVE-2026-63415Jane: $ref resolution performs SSRF + LFI (path traversal) at code-generation time (jane-php)
- CVE-2026-131253Remote Code Execution (RCE) through the App Wizard in Splunk SOAR
- CVE-2026-120539Restrictions for BuddyPress <= 1.5.4 - Unauthenticated Remote Code Execution via Request URI String Interpolation in eval()
- CVE-2026-134253Grav API Plugin 1.0.0 before 1.1.4 RCE via blueprint-upload Theme Template Write
No corrections so far. Something wrong on this page? Report an error.