CVE Identifier Regex for Go

What this pattern does

This page provides a well-structured, multi-part regular expression for matching cve identifier, ported and verified for Go. In security-sensitive code, using an unverified regex can open the door to both false positives and denial-of-service attacks. The snippet below is ready to drop into your Go project — whether you're validating in a Gin handler, a gRPC service, or a command-line tool.

Go Implementation

// CVE Identifier
// ReDoS-safe | RegexVault — Security > Network Security

package validation

import "regexp"

var cveIdentifierRe = regexp.MustCompile(`^CVE-(19[6-9][0-9]|20[0-9]{2})-([0-9]{4,7})$`)

func ValidateCveIdentifier(s string) bool {
    return cveIdentifierRe.MatchString(s)
}

// Example
// fmt.Println(ValidateCveIdentifier("CVE-2021-44228")) // true

Test Cases

When to use this pattern

This pattern is drawn from the Security > Network Security category and carries a ReDoS-safe certification. That matters for Go developers because Go's RE2 engine is inherently safe from catastrophic backtracking, but this pattern has been additionally verified for correctness. 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

Technical Notes

CVE format: CVE-YYYY-NNNNN where YYYY is 1960-present year and NNNNN is at least 4 digits. Notable examples: CVE-2021-44228 (Log4Shell), CVE-2014-0160 (Heartbleed), CVE-2017-5638 (Apache Struts/Equifax breach). Year range starts 1960 (earliest MITRE entry).