Microcks's POST /api/import and POST /api/export endpoints allow non-administrator accessGHSA-r6ph-5fp2-3w2v
MEDIUMFix: microcks/microcks@4bb98d7GHSA-r6ph-5fp2-3w2v is a medium-severity (CVSS 6.5) Improper Privilege Management vulnerability in io.github.microcks:microcks-app. A fix is available for io.github.microcks:microcks-app — see the affected versions and patch details below.
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-r6ph-5fp2-3w2v.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.github.microcks:microcks-appReal-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
In Microcks before 1.10.0, the POST /api/import and POST /api/export endpoints allow non-administrator access.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.github.microcks:microcks-app | all versions | 1.10.0io.github.microcks:microcks-app:1.10.0 |
Affected Products
microcksmicrocksDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.github.microcks:microcks-app, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.github.microcks:microcks-app to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r6ph-5fp2-3w2v is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is GHSA-r6ph-5fp2-3w2v in your dependencies?
Find it across Maven, including transitive dependencies.