CVE
Jane PHP remote code execution in generated API clients
- Exploited
- No known exploitation
- Fix
- Fixed in 7.12.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.12.0.
Summary
A remote attacker who doesn't need to log in can exploit a flaw in Jane, a set of PHP libraries that generate API clients and models, by supplying an attacker-influenced OpenAPI document. The flaw lets arbitrary PHP code run with the privileges of the consuming application once the generated client is instantiated and used.
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 header parameter name verbatim as an array key in generated Client/Endpoint method docblocks. A header parameter name 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- 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
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-63413 (Jane: Instantiation RCE via header parameter name -> 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-63413 (entry last updated 2026-11-18):
Affected:
- janephp janephp: fixed in 7.12.0
Fixed versions: 7.12.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-63413 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63413 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-x9xr-53qx-9qcf
- 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-63413
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-63413"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- janephp janephp
fixed in 7.12.0
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · janephp/janephp · Advisory GHSA-x9xr-53qx-9qcf |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-63413 |
| Record | NVD · CVE-2026-63413 |
| Other links 3 | |
| Repository | GitHub · janephp/janephp · Pull request #960 |
| Repository | GitHub · janephp/janephp · Commit 0ea379de |
| Repository | GitHub · janephp/janephp · Release v7.12.0 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63413
Is CVE-2026-63413 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
Which versions are affected by CVE-2026-63413?
janephp: before 7.12.0.Source: cve.now feed data
How do I fix CVE-2026-63413?
Upgrade to a fixed version: 7.12.0.Source: cve.now feed data