dbcve.org
InjectionWeakness · CWE-74

CVE-2026-15512

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was identified in pig-mesh Pig up to 3.9.2. Affected by this issue is some unknown functionality of the file \pig-master\pig-visual\pig-codegen\src\main\java\com\pig4cloud\pig\codegen\service\impl\GeneratorServiceImpl.java of the component pig-codegen. Such manipulation leads to code injection. It is possible to launch the attack remotely. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Code injection vulnerability in pig-mesh Pig's pig-codegen component (GeneratorServiceImpl.java). The code generation functionality does not properly sanitize input, allowing remote attackers to inject malicious code through the code generation process. The exploit is publicly available.

MitigationImplement strict input validation and sanitization on all user-supplied parameters in GeneratorServiceImpl.java. Use parameterized templates or a sandboxed approach for code generation to prevent injection of arbitrary code. Consider restricting or disabling the code generation feature until a proper fix is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify pig-mesh installation
    Search for pig-mesh or pig-codegen related files, libraries, or services in the environment. Look for directories named 'pig', 'pig-mesh', or 'pig-codegen' and check for JAR files containing 'pig-codegen' in the filename.
    Affected if pig-mesh with the pig-codegen component is present in the environment
  2. Determine pig-codegen version
    Locate the pig-codegen JAR file or compiled classes (particularly GeneratorServiceImpl.java). Check the manifest file or version metadata within the JAR, or compare the file hash against known version releases.
    Affected if The installed version cannot be determined or is earlier than the fixed version (compare against official pig-mesh release notes for the patch date)
  3. Verify code generation feature accessibility
    Identify if the GeneratorServiceImpl code generation endpoint or functionality is exposed. Check configuration files, application properties, or exposed API routes for endpoints related to code generation (often under /codegen, /generate, or similar paths).
    Affected if The code generation feature is enabled and accessible via HTTP/API without authentication or with weak access controls
  4. Inspect code generation templates and output directories
    Examine the templates directory used by pig-codegen (commonly found in the JAR under 'templates' or 'codegen' paths) and any configured output directories. Look for unexpected modifications, backdoor scripts, or unfamiliar template files.
    Affected if Templates contain suspicious code, unexpected files exist in output directories, or new/unknown files are present in template locations
  5. Review application logs for code generation activity
    Search application logs for entries related to GeneratorServiceImpl, code generation requests, or template processing. Look for unusual parameters, errors related to code injection attempts, or unexpected code generation events.
    Affected if Logs show code generation requests with unusual parameters, injection attempts, or unauthorized code generation events

If pig-mesh with pig-codegen is present and the code generation feature (GeneratorServiceImpl) is accessible, the environment is potentially affected by this vulnerability and should be compared against the patched version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and sanitization on all user-supplied parameters in GeneratorServiceImpl.java. Use parameterized templates or a sandboxed approach for code generation to prevent injection of arbitrary code. Consider restricting or disabling the code generation feature until a proper fix is applied.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15512 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data