Security readout for executives and security teams
Plain-English summary
This is a low-severity build-time supply-chain weakness in a Maven parent POM that was published despite being intended only for project testing. If an organization uses that parent POM externally, a compromised template artifact could cause unexpected Mustache files to be unpacked during dependency updates.
Executive priority
Handle through normal dependency hygiene, not emergency response. Prioritize teams using this Maven parent POM in production builds or CI pipelines, then remove or upgrade it.
Technical view
io.github.chrimle:openapi-to-java-records-mustache-templates-parent versions 3.1.1 through before 3.5.1 use maven-dependency-plugin to unpack .mustache files from the related templates artifact. The concern is automatic unpacking if that artifact is compromised, not a direct remote exploit.
Likely exposure
Exposure is likely limited to Java/Maven projects that inherit from or otherwise use the published parent POM, especially in CI or build automation. The project states the parent POM is not intended for external production use.
Exploitation context
The sources do not report active exploitation, and KEV status is false. Abuse appears conditional on a compromised openapi-to-java-records-mustache-templates artifact and a user or build process performing a dependency update.
Researcher notes
The advisory describes a best-practice failure and potential supply-chain pathway rather than confirmed malicious artifacts. Impact depends on external use of a parent POM the project says is intended for tests and maintainability only.
Mitigation direction
- Do not use the parent POM for external production projects.
- Remove inheritance from openapi-to-java-records-mustache-templates-parent where possible.
- Upgrade the parent POM to version 3.5.1 if it remains in use.
- Review vendor guidance before making broader build-process changes.
Validation and detection
- Search Maven POMs for openapi-to-java-records-mustache-templates-parent.
- Confirm any detected version is not 3.1.1 through before 3.5.1.
- Review CI builds for dependency unpacking of .mustache files.
- Verify external projects do not depend on testing-only project modules.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-32735 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 2.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
2.3LowVector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Chrimle/openapi-to-java-records-mustache-templates/security/advisories/GHSA-3hrg-hjvj-9v66CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/Chrimle/openapi-to-java-records-mustache-templates/pull/534CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Chrimle/openapi-to-java-records-mustache-templates/pull/620CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/Chrimle/openapi-to-java-records-mustache-templates/releases/tag/v3.5.1CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.