REGEXVAULTv2.0
Dev & Systems/File Paths
Verified Safe

Unix Absolute Path Regex for Java

/^\/(?!.*\.\.\/)(?!.*\s)(?!.*\n)(?:[^\/\0]+\/?)*$/

What this pattern does

This page provides a comprehensive, battle-tested regular expression for matching unix absolute path, ported and verified for Java. A rigorously tested regex reduces debugging time and protects your application from edge-case failures. The snippet below is ready to drop into your Java project — whether you're validating in a Spring Boot controller, a Jakarta EE service, or a standalone utility class.

Java Implementation

Java
// Unix Absolute Path
// ReDoS-safe | RegexVault — Dev & Systems > File Paths

import java.util.regex.Pattern;

public class UnixAbsolutePathValidator {
    private static final Pattern PATTERN =
        Pattern.compile("^\\/(?!.*\\.\\.\\/)(?!.*\\s)(?!.*\\n)(?:[^\\/\\0]+\\/?)*$");

    public static boolean validate(String input) {
        return PATTERN.matcher(input).matches();
    }

    // Example
    public static void main(String[] args) {
        System.out.println(validate("/")); // true
    }
}

Test Cases

Matches (Valid)
Rejects (Invalid)
/home/user
/home/user//double-slash
/var/log/app.log/path/../traversal
/etc/nginx/sites-enabled/default/path with spaces
/usr/local/bin/python3/path newline

When to use this pattern

This pattern is drawn from the Dev & Systems > File Paths category and carries a ReDoS-safe certification. That matters for Java developers because critical in Java applications since the JVM regex engine uses backtracking and is susceptible to ReDoS without careful pattern design. RegexVault audits patterns against known backtracking attack vectors, ensuring you have the necessary context before using this regex in a high-stakes production environment.

Common Pitfalls

Real Unix paths can contain spaces and special characters the OS allows. This pattern is more restrictive — add space to the class if needed but document the security implication.

Technical Notes

Intentionally restrictive: no spaces, control characters, or path traversal sequences. Use for validated inputs, not for parsing arbitrary filesystem paths which can contain almost any character except NUL.

Have a pattern that belongs in the vault?

Submit it for review — community-verified patterns get credited to your GitHub handle. Free submissions join the queue. Priority review available for $15.

Submit a Pattern