Skip to main content
Menu
CVEs

CVE

Jane PHP path traversal and SSRF in OpenAPI $ref resolution

Affects jane-php before 7.12.0 when PHP code is generated from an attacker-influenced OpenAPI document. Fixed in 7.12.0.

CVE-2026-63415Published Updated Summary written by a model

7.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 7.12.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The victim generates code with jane from an attacker-influenced OpenAPI document. Affects jane-php versions before 7.12.0 (verified on 7.11.2).

Summary

Jane, a PHP library that generates models and API clients from JSON Schema and OpenAPI specifications, fails to restrict OpenAPI `$ref` targets during code generation. A remote attacker, without logging in, can get a victim who generates code from a crafted document to request attacker-chosen or internal services, or to read local JSON or YAML files whose contents end up in the generated output.

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, Jane's Reference.php::doResolve passes an attacker-controlled OpenAPI $ref target to file_get_contents without restricting its scheme or resolved local path. When a victim generates code from an attacker-influenced document, an HTTP or HTTPS reference can cause requests to attacker-chosen or internal services, while an absolute or parent-relative path can read local JSON or YAML files and inline the retrieved content into generated output. Exploitation occurs during generation or CI processing and can disclose local files and internal-service responses. This issue is fixed in version 7.12.0.

Who should check

Teams running jane-php before 7.12.0 that generate PHP code from OpenAPI or JSON Schema documents in build or CI pipelines.

“Generating PHP with jane from an attacker-influenced OpenAPI document”

github.com

cve.now Index

19Pcve.now Index 19 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure12/25Specific setups only, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7/10CVSS 7.0
  • No patch0/5No signal

What would change the score

  • Would score about 69 if added to CISA KEV
  • Would score about 64 if CISA's SSVC rates exploitation active

What to do

  • Check whether your setup matches what the bug needs.

    The victim generates code with jane from an attacker-influenced OpenAPI document. Affects jane-php versions before 7.12.0 (verified on 7.11.2).
  • 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-63415 (Jane: $ref resolution performs SSRF + LFI (path traversal) at code-generation time (jane-php)), 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-63415 (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):
- The victim generates code with jane from an attacker-influenced OpenAPI document. (source: https://github.com/janephp/janephp/security/advisories/GHSA-c3cj-3p6p-j822)
- Affects jane-php versions before 7.12.0 (verified on 7.11.2). (source: https://github.com/janephp/janephp/security/advisories/GHSA-c3cj-3p6p-j822)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-63415 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63415 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-c3cj-3p6p-j822
- https://github.com/janephp/janephp/pull/961
- https://github.com/janephp/janephp/commit/75f2bbf79ca2f2eeb13080a2cebded1263396b49
- 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-63415
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-63415"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • janephp janephp

    fixed in 7.12.0

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · janephp/janephp · Advisory GHSA-c3cj-3p6p-j822
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-63415
RecordNVD · CVE-2026-63415
Other links 3
RepositoryGitHub · janephp/janephp · Pull request #961
RepositoryGitHub · janephp/janephp · Commit 75f2bbf7
RepositoryGitHub · 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-63415

Is CVE-2026-63415 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?

Resolving $ref entries in an OpenAPI document lets an attacker make the jane generator send HTTP requests to attacker-chosen or internal services and read arbitrary local JSON or YAML files through ../ path traversal. The fetched content is inlined into the generated code at build or CI time.Source: github.com

Which versions are affected by CVE-2026-63415?

janephp: before 7.12.0.Source: cve.now feed data

Am I affected, and how do I check?

jane-php versions before 7.12.0 are affected, verified on 7.11.2 with PHP 8.1, when code is generated from an OpenAPI document that an attacker can influence. To check the installed version, look at the jane-php entry in the project's composer.lock file.Source: github.com

How do I fix CVE-2026-63415?

Upgrade jane-php to 7.12.0 or later.Source: github.com

More CVEs