Security Metadata Guide¶
Structured Changelog supports rich security metadata for vulnerability disclosures.
Overview¶
Security entries can include CVE/GHSA identifiers, severity ratings, CVSS scores, and links to SARIF static analysis results. This enables:
- Automated vulnerability tracking
- Integration with security scanners
- Compliance reporting
- Audit trails
Fields¶
CVE (Common Vulnerabilities and Exposures)¶
Format: CVE-YYYY-NNNNN where YYYY is the year and NNNNN is at least 4 digits.
GHSA (GitHub Security Advisory)¶
Format: GHSA-xxxx-xxxx-xxxx where x is lowercase alphanumeric.
Severity¶
Valid values:
critical- Immediate action requiredhigh- High impact, fix soonmedium- Moderate impactlow- Low impactinformational- No immediate risk
CVSS (Common Vulnerability Scoring System)¶
{
"description": "Fix buffer overflow",
"cvssScore": 8.5,
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
Score ranges:
- 9.0-10.0: Critical
- 7.0-8.9: High
- 4.0-6.9: Medium
- 0.1-3.9: Low
CWE (Common Weakness Enumeration)¶
Common CWEs:
- CWE-79: Cross-site Scripting (XSS)
- CWE-89: SQL Injection
- CWE-94: Code Injection
- CWE-287: Improper Authentication
- CWE-798: Hard-coded Credentials
Version Ranges¶
{
"description": "Fix privilege escalation",
"affectedVersions": "<2.0.0",
"patchedVersions": ">=2.0.0"
}
SARIF Integration¶
Link to static analysis results:
Complete Example¶
{
"irVersion": "1.0",
"project": "secure-app",
"releases": [
{
"version": "2.1.1",
"date": "2026-01-03",
"security": [
{
"description": "Fix SQL injection in user search endpoint",
"cve": "CVE-2026-12345",
"ghsa": "GHSA-abcd-efgh-ijkl",
"severity": "high",
"cvssScore": 8.5,
"cvssVector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"cwe": "CWE-89",
"affectedVersions": "<2.1.1",
"patchedVersions": ">=2.1.1",
"sarifRuleId": "go/sql-injection",
"pr": "#123"
}
]
}
]
}
Rendered Output¶
With IncludeSecurityMetadata: true:
### Security
- Fix SQL injection in user search endpoint (CVE-2026-12345, GHSA-abcd-efgh-ijkl, severity: high)
Best Practices¶
- Always include CVE/GHSA when available - Makes tracking easier
- Use severity consistently - Follow your organization's severity definitions
- Include affected versions - Helps users determine if they're impacted
- Link to advisories - Provide full details for those who need them
- Coordinate disclosure - Don't publish before patches are available