How severe is GHSA-fjh6-p566-wr6q?

No CVSS score has been assigned to GHSA-fjh6-p566-wr6q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fjh6-p566-wr6q?

GHSA-fjh6-p566-wr6q affects the following packages: io.github.skylot:jadx-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fjh6-p566-wr6q?

Update io.github.skylot:jadx-core to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fjh6-p566-wr6q is resolved across your whole dependency graph.

How do I detect GHSA-fjh6-p566-wr6q in my Maven dependencies?

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

How do I mitigate GHSA-fjh6-p566-wr6q 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-fjh6-p566-wr6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-fjh6-p566-wr6q 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.

When was GHSA-fjh6-p566-wr6q published, and has it been updated?

GHSA-fjh6-p566-wr6q was published on July 21, 2022 and was last updated on November 28, 2024. 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

skylot jadx affected by Incorrect Behavior Order in vulnerable dependencyGHSA-fjh6-p566-wr6q

GHSA-fjh6-p566-wr6q is a security vulnerability in io.github.skylot:jadx-core. A fix is available for io.github.skylot:jadx-core — see the affected versions and patch details below.

Published

Jul 21, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕io.github.skylot:jadx-core

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

Vulnerable library protobuf-java 3.11.4 (CVE-2021-22569)

Patches

Dependency updated in jadx 1.4.3

References

According to the AquaSecurity report: 05F1C52A666E4FCC844ABD085BD55124

Also, Maven repository have links to this and other vulnerabilities from dependencies: https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java/3.11.4

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.github.skylot:jadx-core`	all versions	1.4.3`io.github.skylot:jadx-core:1.4.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.skylot:jadx-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.github.skylot:jadx-core to 1.4.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fjh6-p566-wr6q is resolved across your whole dependency graph.
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

### Impact Vulnerable library protobuf-java 3.11.4 (CVE-2021-22569) ### Patches Dependency updated in jadx 1.4.3 ### References According to the AquaSecurity report: ![05F1C52A666E4FCC844ABD085BD55124](https://user-images.githubusercontent.com/118523/177364939-087e2144-9a8a-4594-ae90-eb2acb0a2036.png) Also, Maven repository have links to this and other vulnerabilities from dependencies: https://mvnrepository.com/artifact/com.google.protobuf/protobuf-java/3.11.4

O3 Security · Impact-Aware SCA

Is GHSA-fjh6-p566-wr6q in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works