External risk intelligence

Jane PHP Libraries OpenAPI Header Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-63413

The vulnerability exists in a PHP library used during the build-time generation of code. The issue requires an attacker to provide a malicious OpenAPI document to the generator and then for a developer to use the resulting generated SDK. It is not an internet-facing service or runtime component, but rather a developer-side tool used to build applications.

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 critical vulnerability has been identified in the Jane PHP library, which is used to generate code from API specifications. This issue could allow an attacker to inject malicious code into generated client applications if they can influence the API specification used during the generation process. The primary concern is to confirm if this library is used within your development workflows and if the generated code is then deployed.

  • Code generation vulnerability allows remote code execution.
  • Matters if your teams use this tool for API development.
  • Confirm use and exposure in your development lifecycle.

Attack Path

How an attacker could exploit the issue

An attacker could influence the creation of an application's code by providing a specially crafted OpenAPI document to the Jane PHP library. This document, when processed by the library's generator, can embed malicious PHP code within the generated client code. When this generated client is later used, the embedded code can execute arbitrary commands with the privileges of the consuming application.

  • Attacker influences code generation.
  • Malicious OpenAPI document triggers vulnerability.
  • Arbitrary PHP execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an attacker-influenced OpenAPI document could lead to the execution of arbitrary PHP code with the privileges of the consuming application. This occurs when the Jane open-api-3 generator emits a header parameter name containing a PHPDoc closing delimiter, which can prematurely terminate comments and inject malicious PHP during client instantiation.

  • Application code and sensitive data.
  • Via crafted OpenAPI schema during code generation.
  • Arbitrary code execution with application privileges.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts the development lifecycle, specifically the code generation phase. Teams responsible for managing development tools and build pipelines are likely to be affected. The initial practical move involves identifying where OpenAPI specifications are processed, confirming if these specifications are sourced from untrusted environments, and then engaging the development leads or application owners to update the Jane library used in the generation process.

  • Ownership: Development tooling and build teams.
  • Verify: Untrusted OpenAPI specs in use.
  • Action: Update Jane library in CI/CD.

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?

Jane is a collection of PHP libraries designed to automate development tasks. It is primarily used by developers to build API clients and data models automatically by parsing OpenAPI or JSON Schema specifications, which helps ensure code consistency and reduces manual boilerplate when connecting to external services.

What is the vulnerability in CVE-2026-63413?

This is a code injection vulnerability, categorized as CWE-94. It happens when the Jane generator improperly handles header names found in API specifications. If a header name contains specific characters, it can escape the intended documentation comments and inject raw PHP code directly into the generated class file, which then executes whenever that class is initialized.

How can an attacker trigger this bug?

An attacker must successfully influence the OpenAPI document used during the automated code generation process. The vulnerability is not triggered by simply visiting an application or sending a request to a running server; it specifically requires the generator to process a malicious schema file during a build or development workflow.

Is my infrastructure at risk according to Halo Surface Signal?

Halo Surface Signal notes that this is an unlikely threat because the vulnerability resides in build-time tooling rather than an internet-facing runtime service. Because this is a developer-side issue occurring before an application is even built or deployed, it is not considered a direct network-accessible exposure for your live production services.

How do I fix this in my development process?

The primary fix is to update the Jane library to version 7.12.0 or later within your development and CI/CD pipelines. You should also audit your build configurations to ensure that any OpenAPI specifications being used to generate SDKs are sourced from trusted, internal locations rather than external or unverified inputs.

References