Security Advisory & CVE Vulnerability Matrix Markdown Table Template
Track security advisories, CVE identifiers, CVSS v3 ratings, affected library versions, patched releases, and remediation guidance.
Interactive Template Customizer
Edit cells, add rows, or sort — changes update the markdown liveColumn Architecture & Alignment Specification
Carefully chosen column alignments ensure optimal visual scannability across desktop and mobile screens:
| Column Header | Alignment | Delimiter Syntax | Design Rationale |
|---|---|---|---|
| CVE Identifier | left | :--- | Standard left-aligned readable text & descriptions |
| Affected Component | left | :--- | Standard left-aligned readable text & descriptions |
| CVSS v3 | center | :---: | Centers compact status symbols, flags, or tags |
| Severity | center | :---: | Centers compact status symbols, flags, or tags |
| Vulnerable Versions | center | :---: | Centers compact status symbols, flags, or tags |
| Patched In | right | ---: | Aligns numeric scale, defaults, or magnitudes |
Pro Tips for Security Advisory & CVE Vulnerability Matrix
- Link CVE IDs directly to NIST or MITRE databases: `[CVE-2025-1082](https://nvd.nist.gov/...)`.
- Center-align severity badges (Critical, High, Medium, Low) and CVSS scores.
- Always specify the exact patched version so users know when to upgrade.
How to Deploy This Table Across Platforms
Paste raw Markdown into README.md. Leave one blank newline above and below for GFM compliance.
Paste directly into Live Preview mode. Use wikilinks ([[Note]]) inside cells for bidirectional linking.
Press Enter to make a fresh empty line block, then paste. Notion auto-transforms it into a native Simple Table block.
Standard GFM tables work out of the box in modern MDX engines. You can style them via custom CSS selectors.
Raw GFM Code
| CVE Identifier | Affected Component | CVSS v3 | Severity | Vulnerable Versions | Patched In |
| :-------------- | :-------------------------------------- | :-----: | :----------: | :-----------------: | ---------: |
| `CVE-2025-2140` | JSON Deserializer | `9.8` | **CRITICAL** | `< 2.0.4` | `v2.0.4` |
| `CVE-2025-1988` | LaTeX Exporter Command Injection | `8.1` | **HIGH** | `< 1.9.8` | `v1.9.9` |
| `CVE-2024-9912` | CSV Prototype Pollution | `5.3` | MEDIUM | `< 1.8.2` | `v1.8.3` |
| `CVE-2024-8501` | ReDoS in Markdown Table Alignment Regex | `4.2` | LOW | `< 1.7.0` | `v1.7.1` |Standard padded style with boundary pipes matching GitHub GFM parser specifications.
Platform Support
Syntax Formatting Rules
- Pipe Escaping: Use
\|for text with pipe symbols. - Multi-line Cells: Use
<br>for line breaks. - Monospace Text: Wrap variables or code in backticks (
`key`). - Empty Values: Use
—instead of leaving cells empty.
More Developer Markdown Templates
Browse all 50 templatesREST & GraphQL API Parameters
Document REST endpoints, GraphQL query fields, request payload types, requirements, and default fallback values.
Environment Variables (.env) Matrix
Document required and optional environment keys, secret classifications, types, and staging vs production defaults.
CLI Options & Arguments Reference
Reference table for command-line tool options, shorthand aliases, data types, environment overrides, and descriptions.
Frequently Asked Questions About Security Advisory & CVE Vulnerability Matrix
How should I format parameters, flags, or keys in this Security Advisory & CVE Vulnerability Matrix table?
Wrap variable names in the "CVE Identifier" column in backticks (e.g., `CVE-2025-2140`). This enforces monospace rendering, prevents underscores from italicizing surrounding text, and improves readability across GitHub and developer documentation sites.
Where in my repository or project documentation should I place this Security Advisory & CVE Vulnerability Matrix table?
This template is specifically designed for github repository security.md files, soc2 compliance security audits, open-source vulnerability disclosure logs. Place it inside your project's README.md, technical wiki, or developer portal. Always leave at least one blank newline before and after the table to ensure the GFM parser detects it properly.
Why is the "CVE Identifier" column styled with left alignment?
The "CVE Identifier" column functions as the primary key of this table. Setting it to left alignment establishes an anchor along the left reading margin, making it effortless for developers to scan down the list.
How do I add line breaks inside a single cell of this Security Advisory & CVE Vulnerability Matrix table?
Standard Markdown table rows cannot contain literal carriage returns. To create a multi-line list inside a cell, insert HTML <br> tags (e.g. "Item 1<br>Item 2<br>Item 3"). This keeps the entire entry in a single clean row without breaking column alignments.
How do I handle optional or missing values in Security Advisory & CVE Vulnerability Matrix?
Never leave table cells completely empty, as some strict Markdown parsers may collapse empty pipes. Instead, insert an em-dash ("—"), "N/A", or "None" to explicitly indicate that a value is not applicable.
Can I export this Security Advisory & CVE Vulnerability Matrix table into CSV, Excel, or HTML?
Yes. In the interactive toolkit above, you can edit your data and use our integrated export tools to convert this table directly into CSV, JSON, HTML <table>, or LaTeX with a single click.