Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:golang/github.com/ctfer-io/romeo

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

CVE-2026-32805 is a high-severity path traversal vulnerability in the ctfer-io romeo tool versions prior to 0.2.2. The flaw exists in the sanitizeArchivePath function, which incorrectly validates archive paths due to a missing trailing path separator check. This allows a crafted tar archive to write files outside the intended extraction directory, potentially overwriting critical files or placing malicious files on the system. The vulnerability requires no authentication or user interaction and can be exploited remotely if an attacker can supply a malicious archive. The issue affects Go applications using romeo for code coverage measurement in GitHub Actions workflows. Version 0.2.2 of romeo fixes this vulnerability.

Join the discussion

Romeo gives the capability to reach high code coverage of Go ≥1.20 apps by helping to measure code coverage for functional and integration tests within GitHub Actions. Prior to version 0.2.1, due to a mis-written NetworkPolicy, a malicious actor can pivot from the "hardened" namespace to any Pod out of it. This breaks the security-by-default property expected as part of the deployment program, leading to a potential lateral movement. Removing the `inter-ns` NetworkPolicy patches the vulnerability in version 0.2.1. If updates are not possible in production environments, manually delete `inter-ns` and update as soon as possible. Given one's context, delete the failing network policy that should be prefixed by `inter-ns-` in the target namespace.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Package: pkg:golang/github.com/ctfer-io/romeo
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses