External risk intelligence

Jane PHP OpenAPI Generator Code Injection

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-63412

This vulnerability exists in a PHP library used at build-time to generate API client code. The issue is triggered during the development or build process by processing a malicious OpenAPI schema. It does not exist in a running public-facing service itself, but rather within the development toolchain used to create software components.

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

This vulnerability involves the Jane PHP library, which is used to generate code from API specifications. A flaw in the code generation process could allow an attacker to inject malicious code that would execute with the privileges of the consuming application when a generated client is instantiated. The main concern is confirming relevance and exposure.

  • Code generation flaw allows attacker code execution.
  • Matters if your code generation process uses this library.
  • Assess if this library is used in your development lifecycle.

Attack Path

How an attacker could exploit the issue

An attacker could compromise an application by providing a specially crafted OpenAPI document to the Jane library during its client generation phase. This malicious document, when processed by the vulnerable Jane open-api-3 generator, can lead to the insertion of attacker-controlled PHP code within the generated client's class body. If this generated client is then instantiated, the embedded PHP code will execute with the privileges of the consuming application.

  • Attacker influences OpenAPI document.
  • Malicious parameter name triggers code injection.
  • Arbitrary PHP code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could affect PHP applications that use generated client code from the Jane library when consuming an OpenAPI document. When supported by the advisory, an attacker-influenced OpenAPI document, when processed by the Jane open-api-3 generator, could lead to the execution of arbitrary PHP code within the privileges of the consuming application.

  • Generated client code.
  • Malicious OpenAPI schema processed.
  • Arbitrary PHP code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Jane affects the build process, not a running service. Teams responsible for the software development lifecycle, including developers and platform engineers, should address this by identifying where the affected code generation occurs and ensuring a secure build environment. The first practical step is to review the CI/CD pipeline and any local development environments that utilize the Jane library to generate client code.

  • Owner: Development and platform engineering teams.
  • Verify: Affected code generation process is secure.
  • Action: Update Jane library in build tooling.

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 the Jane library used for?

Jane is a collection of PHP libraries that automates the creation of models and API clients. Developers use it to transform standard API definitions, specifically those written in JSON Schema or OpenAPI, into ready-to-use PHP code. By generating these clients automatically, it simplifies the process of integrating external services into a PHP application.

What does CVE-2026-63412 mean for code safety?

This vulnerability is a code injection flaw. Because the tool improperly handles specific naming patterns in OpenAPI documents, it can inadvertently place unauthorized PHP commands into the files it generates. When the application later initializes these generated components, it executes the injected commands, which could lead to unauthorized actions performed with the application's own system permissions.

How is this vulnerability triggered?

The issue is triggered only when the Jane library processes a malicious or untrusted OpenAPI specification document to generate client code. It does not occur if you are simply running an application that uses already-generated, clean client code. The injection requires that the build process itself consumes a manipulated specification file containing specific delimiters.

Is my service at risk according to Halo Surface Signal?

According to Halo Surface Signal, this vulnerability is very unlikely to affect a running public-facing service directly. Because the flaw exists within the build-time development toolchain rather than in the service code itself, the risk is tied to your development lifecycle and automated build pipelines where the code generation occurs.

What should I do if I use Jane to build my software?

Your primary step is to update the Jane library to version 7.12.0 or higher in your development environment and CI/CD pipelines. Since this is a build-time issue, you should also review your internal processes to ensure that any OpenAPI documents used to generate client code are sourced from trusted locations and validated before processing.

References