SecPod

Learn Search

Search across all Learn content

← Back to Security Research

SecPod produces security advisories in CVRF format

SecPod intends to publish security advisories in an XML format that conforms to Common Vulnerability Reporting Format (CVRF version 1.1).

Jun 5, 2013By Antu1 min read

SecPod intends to publish security advisories in an XML format that conforms
to Common Vulnerability Reporting Format (CVRF version 1.1).

What is CVRF?
The Common Vulnerability Reporting Framework is an XML-based standard that
enables sharing of vulnerability information in a machine-readable format.
Originally derived from the Internet Engineering Task Force (IETF) draft Incident
Object Description Exchange Format (IODEF), this format was then developed by
the Industry Consortium for Advancement of Security on the Internet (ICASI).

CVRF Provides Two Key Benefits:
(1) It provides a consistent way to depict security information thus simplifying
the interpretation of the advisories, and
(2) It provides a machine-readable format for the interpretation of security
advisories, thus allowing automation (and integration of the advisories in,
for example, vulnerability scanning tools).

One of our advisory in CVRF format:
Advantech WebAccess HMI/SCADA Software Persistence Cross-Site Scripting Vulnerability.

Featured Posts

Open WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels
WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

CVE Research

WHIPSHOT and SLAPSHOT: Citrix NetScaler Zero-Days Exploited to Plant Root Web Shells and Internal Tunnels

Oct 1, 2026

Open OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure
OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

CVE Research

OpenSSL’s DTLS State Handling Error Opens the Door to Heap Data Exposure

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions
Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

CVE Research

Patch Analysis & Exploitation Timeline: Critical WSO2 and Adobe Flaws Show 1-Day vs. 133-Day Exploitation Window , September 24, 2026 KEV Additions

Two critical vulnerabilities added to CISA KEV on September 24, 2026 reveal sharply different exploitation timelines. CVE-2026-71362 saw publicly documented exploitation roughly one day after Adobe's patch release, while CVE-2026-5430 had a 133-day vendor-remediation-to-observed-exploitation interval.

Oct 1, 2026

Open Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026
Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

CVE Research

Patch Analysis & Exploitation Timeline: Same-Week KEV Additions, Year-Apart Patch Dates - Linux Kernel, September 18, 2026

Three Linux kernel vulnerabilities entered CISA’s KEV catalog on September 18, 2026, although their Linux 6.12 fixes were available 91–386 days earlier. This analysis separates patch availability, CVE publication, and known-exploitation status without treating KEV dates as first-attack dates.

Sep 28, 2026