Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2021-32769: 1.73% estimated exploitation activity in the next 30 days; percentile 77.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

With a basic configuration like it is possible to access any file from a filesystem, using "/../../" in URL, as Micronaut does not restrict file access to configured paths. Repro Steps - create a file test.txt in /home/lstrmiska - start micronaut - execute command curl -v --path-as-is "http://localhost:8080/.assets/public/../test.txt" Impact Micronaut can potentially leak sensitive information. See https://cwe.mitre.org/data/definitions/22.html Patches Workarounds - do not use in mapping, use only which exposes only flat structure of a directory not allowing traversal - run micronaut in chroot (linux only) References See https://cwe.mitre.org/data/definitions/22.html For more information If you have any questions or comments about this advisory: Open an issue in Github Email us at info@micronaut.io

Published by the source

26 Jul 2021, 21:15 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cjx7-399x-p2rj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2021-32769

Advisory: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in micronaut-core
IDs: CVE-2021-32769, GHSA-cjx7-399x-p2rj
Record: https://patchnext.com/advisories/cve-2021-32769 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.micronaut:micronaut-http-server-netty 2.5.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.micronaut:micronaut-http-server-netty: affected < 2.5.9; fixed in 2.5.9

## Suggested inspection (read-only)
- Maven io.micronaut:micronaut-http-server-netty: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.micronaut:micronaut-http-server-netty.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cjx7-399x-p2rj (GitHub-reviewed advisory GHSA-cjx7-399x-p2rj lists affected ranges: Maven io.micronaut:micronaut-http-server-netty >=0 <2.5.9)

Commands are suggestions: review each one before running it.