Skip to main content
Mallory
HighVulnerability

CVE-2025-33042: Code Injection in Apache Avro Java SDK Specific Record Generation

Published Feb 13, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.3High · v3.1
EPSS0.63%51st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apache Software Foundation
IdentifiersCVE-2025-33042CWE-94 · Improper Control of Generation of…

CVE-2025-33042 is an improper control of code generation vulnerability in the Apache Avro Java SDK. When generating Java specific-record classes from an untrusted Avro schema, attacker-controlled schema content can be incorporated into generated Java source in a manner that permits code injection. Apache Avro Java SDK releases through 1.11.4 and release 1.12.0 are affected.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker able to supply an Avro schema to a vulnerable specific-record generation workflow can inject attacker-controlled Java code into generated source. If that source is subsequently compiled or otherwise processed in an execution-capable build or processing environment, this can potentially result in execution of attacker-controlled code with the privileges of that environment.

Mitigation

If you can’t patch tonight, do this now.

Do not generate specific records from untrusted Avro schemas until fixed versions are deployed. Restrict schema ingestion to authenticated and trusted sources, validate and review schemas before code generation, and isolate code-generation and build workloads using least-privilege execution environments.

Remediation

Patch, then assume compromise.

Upgrade Apache Avro Java SDK to version 1.11.5, 1.12.1, or a later fixed release. Ensure all code-generation components and build environments use the updated Avro dependency.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Apache Software FoundationAvroapplication
FAQ

Frequently asked questions

Is CVE-2025-33042 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-33042 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-33042?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-33042.
Is there a patch for CVE-2025-33042?
Upgrade Apache Avro Java SDK to version 1.11.5, 1.12.1, or a later fixed release. Ensure all code-generation components and build environments use the updated Avro dependency.
What products are affected by CVE-2025-33042?
Apache Software Foundation Avro.
How severe is CVE-2025-33042?
CVE-2025-33042 has a CVSS v3.1 score of 7.3 (High) and an EPSS score of 0.63% (51st percentile) as of Sep 25, 2026.
Activity feed

Recent activity

12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity10Community discussion across Reddit, Mastodon, and other social sources.