External risk intelligence

Jane PHP Libraries Code Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-63411

This vulnerability exists in a PHP library used during development or build-time to generate API client code. The issue resides within the generated source code of applications, not in a runtime service or internet-facing appliance. Because this is a developer-centric tool used to build other software, it lacks direct public network exposure.

Code Injection

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability has been identified in the Jane PHP library that could allow for the execution of arbitrary PHP code when generating client code from an OpenAPI document. This issue occurs because a parameter description within the OpenAPI specification is directly embedded into generated documentation, and a specially crafted description can inject malicious PHP code that executes when the generated client is instantiated.

  • Injected code can run on client instantiation.
  • Understand how generated code might be impacted.
  • Verify if your development process uses this tool.

Attack Path

How an attacker could exploit the issue

An attacker could craft a malicious OpenAPI document to influence the code generation process. When a developer integrates this generated code into an application, a specially formatted parameter description can trick the PHP interpreter into executing arbitrary code with the application's permissions.

  • No user interaction needed.
  • Malicious OpenAPI document.
  • Arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker could inject malicious PHP code into generated client code. This could occur if an attacker influences the OpenAPI document used to generate the client, and then the generated client is instantiated. The injected code would execute with the privileges of the consuming application.

  • Generated client code.
  • Attacker-influenced OpenAPI document.
  • Arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for application development and the build pipeline should investigate this vulnerability. The first practical step is to identify all projects that use Jane to generate API clients, determine if these generated clients are used in production or sensitive environments, and confirm the accountable owner for each affected application or service before planning remediation.

  • Application development teams own the issue.
  • Verify client generation and usage in production.
  • Plan remediation during the next maintenance window.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Jane and how is it used in software development?

Jane is a collection of PHP libraries designed to automate development tasks. Developers use it to ingest JSON Schema and OpenAPI specifications to automatically generate functional API clients and data models. By turning these specifications into ready-to-use SDKs, it reduces manual coding and ensures the client stays synchronized with the API definition during the build process.

How does CVE-2026-63411 lead to code execution?

This vulnerability is a form of code injection. When Jane processes an OpenAPI document, it takes parameter descriptions and places them into documentation blocks (docblocks) in the generated source code. If a description contains specific characters that terminate a comment early, an attacker can escape the documentation block and inject raw PHP code. This code becomes part of the class, executing whenever the generated client object is instantiated by the application.

Do I need an attacker to interact with my app to trigger this?

No. The vulnerability is triggered during the software development or build phase, not by a runtime user. It requires an attacker to provide a malicious OpenAPI document that Jane then uses to generate code. If you use a trusted, internal OpenAPI specification that has not been tampered with, this specific injection path does not trigger.

Is my application at risk if it uses a Jane-generated client?

Halo Surface Signal indicates this is unlikely because the flaw exists in build-time tooling rather than a public-facing service. The risk only becomes relevant if your development pipeline consumes OpenAPI documents from untrusted sources. If you only generate code from internal or verified API definitions, the attack surface is significantly restricted.

What is the recommended first step to address this CVE?

Start by auditing your development and build pipelines to identify which projects utilize Jane for client generation. Once you have an inventory, verify the sources of the OpenAPI documents being used. Prioritize updating Jane to version 7.12.0 or higher in those environments to ensure the generator safely handles parameter descriptions and prevents code injection.

References