Skip to main content

Threats Tagged 'cve-2026-39395'

View all threats tagged with 'cve-2026-39395'. Filter and sort to focus on specific types of threats.

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):Tag: cve-2026-39395

Threats Tagged 'cve-2026-39395'

Click on any threat for detailed analysis and mitigation recommendations

0

This update for cosign fixes the following issue - CVE-2026-39395: Incorrect attestation verification due to malformed payloads or mismatched predicate types (bsc#1261859). Changes for cosign: - update to 3.0.6: * Fix DSSE predicate check (GHSA-w6c6-c85g-mmv6) (#4801) * Handle whitespace-only certificate annotation (#4760) * fix(sign): closing SignerVerifier too early when signing with a security key (#4761) * Disallow --new-bundle-format and --rfc3161-timestamp (#4762) * support managed keys in conformance testing (#4728) * Add support for GCE metadata server env var (#4732) * fix: preserve per-layer annotations in WriteAttestationsReferrer (#4709) * Fix parsing of in-toto for string predicates * Mark batch of flags for deprecation (#4698) * disallow key and cert identity being used together during verification (#4636) * support key creation in GitLab group (#4704) - Set CGO_ENABLED=1 for fixing s390x failed build - build against a maintained golang version (upstream uses go1.20)

Join the discussion

Cosign versions prior to 3.0.6 and 2.6.3 contain a vulnerability where the verify-blob-attestation command may incorrectly report a successful verification for attestations with malformed payloads or mismatched predicate types. This occurs due to improper error handling and bypass of predicate type validation in different bundle formats. The issue is fixed in versions 3.0.6 and 2.6.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-39395
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses