How severe is GHSA-2j6v-xpf3-xvrv?

GHSA-2j6v-xpf3-xvrv has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-2j6v-xpf3-xvrv?

GHSA-2j6v-xpf3-xvrv affects the following packages: com.wire:avs (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2j6v-xpf3-xvrv?

Update com.wire:avs to 7.1.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2j6v-xpf3-xvrv is resolved across your whole dependency graph.

How do I detect GHSA-2j6v-xpf3-xvrv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.wire:avs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2j6v-xpf3-xvrv if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-2j6v-xpf3-xvrv actively exploited in the wild?

No public exploit code has been indexed for GHSA-2j6v-xpf3-xvrv 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-2j6v-xpf3-xvrv?

GHSA-2j6v-xpf3-xvrv has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th 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-2j6v-xpf3-xvrv?

GHSA-2j6v-xpf3-xvrv is classified as CWE-134 (CWE-134). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2j6v-xpf3-xvrv published, and has it been updated?

GHSA-2j6v-xpf3-xvrv was published on March 1, 2022 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

Use of Externally-Controlled Format String in wire-avsGHSA-2j6v-xpf3-xvrv

CRITICALFix: wireapp/wire-avs@40d373e

GHSA-2j6v-xpf3-xvrv is a critical-severity (CVSS 9.8) CWE-134 vulnerability in com.wire:avs. A fix is available for com.wire:avs — see the affected versions and patch details below.

Also known asCVE-2021-41193

Published

Mar 1, 2022

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2j6v-xpf3-xvrv.

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-2j6v-xpf3-xvrv by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 384,993 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.wire:avs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A remote format string vulnerability allowed an attacker to cause a denial of service or possibly execute arbitrary code.

Patches

The issue has been fixed in wire-avs 7.1.12 and is already included on all Wire products (currently used version is 8.0.x)

Workarounds

No workaround known

References

Fixed in commit https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe

For more information

If you have any questions or comments about this advisory feel free to email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.wire:avs`	all versions	7.1.12`com.wire:avs:7.1.12`

Affected Products

1 product · 1 configurations

Application

wire-audio video signalingwire

< 7.1.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.wire:avs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.wire:avs to 7.1.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2j6v-xpf3-xvrv is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact A remote format string vulnerability allowed an attacker to cause a denial of service or possibly execute arbitrary code. ### Patches * The issue has been fixed in wire-avs 7.1.12 and is already included on all Wire products (currently used version is 8.0.x) ### Workarounds * No workaround known ### References * Fixed in commit https://github.com/wireapp/wire-avs/commit/40d373ede795443ae6f2f756e9fb1f4f4ae90bbe ### For more information If you have any questions or comments about this advisory feel free to email us at [[email protected]](mailto:vulnerability-report@wi