How severe is GHSA-6pmg-vc6m-6wrr?

No CVSS score has been assigned to GHSA-6pmg-vc6m-6wrr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6pmg-vc6m-6wrr?

Affected package information for GHSA-6pmg-vc6m-6wrr is not yet fully mapped. Check the official advisory links for details.

How do I fix GHSA-6pmg-vc6m-6wrr?

Upgrade the affected component to the fixed release for GHSA-6pmg-vc6m-6wrr, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect GHSA-6pmg-vc6m-6wrr in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate GHSA-6pmg-vc6m-6wrr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6pmg-vc6m-6wrr actively exploited in the wild?

No public exploit code has been indexed for GHSA-6pmg-vc6m-6wrr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6pmg-vc6m-6wrr?

GHSA-6pmg-vc6m-6wrr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 23th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6pmg-vc6m-6wrr?

GHSA-6pmg-vc6m-6wrr is classified as CWE-1336 (CWE-1336). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6pmg-vc6m-6wrr published, and has it been updated?

GHSA-6pmg-vc6m-6wrr was published on October 29, 2026 and was last updated on October 30, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Frappe Framework before 15.111.0 and 16.x before…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs23th percentile — riskier than 23% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Frappe Framework before 15.111.0 and 16.x before 16.21.0 contains a server-side template injection vulnerability because user-controlled message fields are rendered as templates without neutralization. An authenticated attacker holding a common operational role can inject template expressions that the server evaluates in an unrestricted context.

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for GHSA-6pmg-vc6m-6wrr, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Frappe Framework before 15.111.0 and 16.x before 16.21.0 contains a server-side template injection vulnerability because user-controlled message fields are rendered as templates without neutralization. An authenticated attacker holding a common operational role can inject template expressions that the server evaluates in an unrestricted context.

O3 Security · Impact-Aware SCA

Is GHSA-6pmg-vc6m-6wrr in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works

Frappe Framework before 15.111.0 and 16.x before 16.21.0 Server-Side Template Injection via Message FieldsGHSA-6pmg-vc6m-6wrr

EPSS Exploitation Probability

Description

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-6pmg-vc6m-6wrr in your dependencies?