{ "updated": "2026-10-08", "presentation": { "highlights": [ { "finding_id": "F-TEKTON-001-001", "record_id": "CVE-2026-33211", "title": "Tekton git resolver path traversal", "summary": "A tenant reaches cluster-wide secrets through a path-boundary failure in a shared resolver.", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c" }, { "finding_id": "F-OPENSSL-OCSP-001", "record_id": "1SEAL-2026-009", "title": "OpenSSL stapled OCSP responder authorization", "summary": "A response signature can validate while the signer is not authorized to answer for the certificate. The reported gap concerns OpenSSL 3.6 stapled OCSP verification.", "source_url": "https://github.com/openssl/openssl/pull/30323" }, { "finding_id": "F-BUILDKIT-001-001", "record_id": "CVE-2026-33747", "title": "BuildKit ContainerID path traversal", "summary": "A ContainerID path escapes the runc executor root during a build: an identifier crosses a filesystem boundary.", "source_url": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj" }, { "finding_id": "F-LEDGER-BTC-MERKLE-001", "record_id": "1SEAL-2026-005", "title": "Ledger Bitcoin signing-path merkle binding bypass", "summary": "A reported merkle preimage binding failure bypasses a signing-path integrity gate. This is not a claim about every device or deployed version.", "source_url": "/research/advisories/1SEAL-2026-005" }, { "finding_id": "F-TORVALDS-LINUX-BT-SMP-001", "record_id": "CVE-2026-43334", "title": "Linux Bluetooth legacy pairing without MITM protection", "summary": "Bluetooth SMP legacy pairing satisfies BT_SECURITY_HIGH without MITM protection: the flag asserts a property the transport does not have.", "source_url": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7" } ] }, "advisories": [ { "id": "CVE-2026-8763", "finding_id": "F-BC-NC-TRAILINGDOT-001", "repo": "bcgit/bc-java", "url": "https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908763", "title": "Name Constraints bypass via trailing dot in rfc822Name and URI", "patched": "BC 1.85; BC-LTS 2.73.12; BC-FJA bc-fips 1.0.2.7, 2.0.2 and 2.1.3", "status": "patched", "kind": "cve", "source_reviewed": "2026-10-05", "credit": "Alex Gaynor with Claude and Anthropic Research; 1seal (Oleh Konko)", "note": "Bouncy Castle publicly credits both researchers for CVE-2026-8763. Its published description concerns trailing-dot handling in rfc822Name and URI constraints; the existing F-BC-NC-TRAILINGDOT-001 fix record describes DNS-name normalization. The vendor associated that report with this CVE in correspondence, but this entry does not assert that the published CVE description covers every DNS or C# behavior in the original record. Multi-at-sign parsing is a separate hardening contribution without a CVE assignment.", "classification": { "area": "identity", "reason": "Trailing-dot email and URI host names can evade excluded certificate name constraints.", "source": "https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908763", "reviewed": "2026-10-05" }, "related_sources": [ { "label": "Published GitHub advisory", "url": "https://github.com/advisories/GHSA-9pwp-9qqc-pr26" } ], "cve_publication": { "id": "CVE-2026-8763", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-8763", "fetched_at": "2026-10-05T04:34:17Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-BC-NC-TRAILINGDOT-001/", "source_url": "https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908763", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-26287", "finding_id": "F-ESO-LABELBYPASS-001", "repo": "external-secrets/external-secrets", "url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "title": "Label enforcement bypass in webhook generator enables secret exfiltration", "patched": "external-secrets v1.3.2; v2.0.0+", "status": "patched", "kind": "cve", "cvss": 7.1, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N", "cvss_assessment": { "version": "3.1", "score": 7.1, "vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N", "assessor": "external-secrets GitHub advisory", "source_url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "observed_at": "2026-10-06" }, "credit": "@1seal: reporter (accepted); @evrardj-roche: reporter; @gusfcarvalho: remediation developer", "note": "GHSA-q7hv-xx6h-q2x8 was published on 2026-10-06 and credits @1seal as a reporter. Webhook generator initialization clears EnforceLabels, allowing an authorized generator creator to reference an unlabeled same-namespace Secret for an outbound webhook. GitHub lists CVE-2026-26287, but the CVE List entry remained RESERVED at the recorded check; this advisory is counted as a published GHSA, not a published CVE, until that state changes.", "classification": { "area": "authorization", "reason": "Webhook generator initialization bypasses the intended secret-label authorization gate.", "source": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "reviewed": "2026-10-06" }, "related_sources": [ { "label": "Public fix PR #5901", "url": "https://github.com/external-secrets/external-secrets/pull/5901" } ], "upstream": { "schema_version": "1.0", "source_url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "resolved_url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "api_url": "https://api.github.com/repos/external-secrets/external-secrets/security-advisories/GHSA-q7hv-xx6h-q2x8", "state": "published", "ghsa_id": "GHSA-q7hv-xx6h-q2x8", "cve_id": "CVE-2026-26287", "summary": "Label enforcement bypass in webhook generator enables secret exfiltration", "published_at": "2026-10-06T09:50:45Z", "updated_at": "2026-10-06T09:50:45Z", "withdrawn_at": null, "fetched_at": "2026-10-06T10:07:23Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "github.com/external-secrets/external-secrets", "ecosystem": "go", "affected": "v0.10.0–v1.3.1", "patched": "v1.3.2; v2.0.0+" } ] }, "cve_publication": { "id": "CVE-2026-26287", "state": "RESERVED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-26287", "fetched_at": "2026-10-06T10:07:23Z" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-ESO-LABELBYPASS-001/", "source_url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8", "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-105712", "finding_id": "F-GNUPG-001-002", "repo": "gnupg/gnupg", "url": "https://cveawg.mitre.org/api/cve/CVE-2026-105712", "title": "gpgtar can write outside the selected extraction directory through a pre-existing symlink", "patched": "GnuPG 2.5.19", "status": "patched", "kind": "cve", "cvss": 3.6, "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L", "cvss_assessment": { "version": "3.1", "score": 3.6, "vector": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L", "assessor": "MITRE CVE record", "source_url": "https://cveawg.mitre.org/api/cve/CVE-2026-105712", "observed_at": "2026-10-06" }, "note": "The published CVE applies to gpgtar before 2.5.19 when extraction with --directory targets an existing directory containing a pre-existing symlink. A fresh empty extraction directory does not have this risk; writes remain limited by the extraction user permissions. The existing F-GNUPG-001-002 record documents the public fix and GnuPG T8159 reporter acknowledgement.", "classification": { "area": "authorization", "reason": "A pre-existing symlink can redirect extracted output outside the selected directory.", "source": "https://cveawg.mitre.org/api/cve/CVE-2026-105712", "reviewed": "2026-10-06" }, "related_sources": [ { "label": "GnuPG T8159", "url": "https://static.dev.gnupg.org/T8159.html" }, { "label": "Public fix commit", "url": "https://github.com/gpg/gnupg/commit/7a2692fe5e580ae3bbb2a47abc4baaf1af65aa88" } ], "cve_publication": { "id": "CVE-2026-105712", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-105712", "fetched_at": "2026-10-06T10:07:23Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-GNUPG-001-002/", "source_url": "https://cveawg.mitre.org/api/cve/CVE-2026-105712", "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-104994", "finding_id": "F-TRIVY-TF-FILE-001", "repo": "aquasecurity/trivy", "url": "https://cveawg.mitre.org/api/cve/CVE-2026-104994", "title": "Trivy Terraform filesystem functions read paths above the scan root", "patched": "Trivy 0.71.0", "status": "patched", "kind": "cve", "cvss": 2.5, "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N", "cvss_assessment": { "version": "3.1", "score": 2.5, "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N", "assessor": "MITRE CVE record", "source_url": "https://cveawg.mitre.org/api/cve/CVE-2026-104994", "observed_at": "2026-10-06" }, "note": "The published CVE covers Trivy before 0.71.0 when Terraform filesystem functions access paths above the scan root during misconfiguration scanning of untrusted input. Exposure requires sensitive data at an unintended path and visibility of that value in scan output. The vendor advisory GHSA-87hp-4m93-274g remains closed and is not presented as a published advisory.", "classification": { "area": "authorization", "reason": "Terraform filesystem functions can read outside the scan root.", "source": "https://cveawg.mitre.org/api/cve/CVE-2026-104994", "reviewed": "2026-10-06" }, "related_sources": [ { "label": "Public fix commit", "url": "https://github.com/aquasecurity/trivy/commit/9d91b888cf63023e9c09b64259a4c1cea8dfe993" } ], "cve_publication": { "id": "CVE-2026-104994", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-104994", "fetched_at": "2026-10-06T10:07:23Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TRIVY-TF-FILE-001/", "source_url": "https://cveawg.mitre.org/api/cve/CVE-2026-104994", "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-79705", "finding_id": "F-BUILDAH-SYMLINK-001", "repo": "podman-container-tools/buildah", "url": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "patched": "go.podman.io/buildah/copier 1.43.4 / 1.45.1", "status": "patched", "kind": "cve", "cvss": 6.1, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L", "note": "GHSA-3528-5p26-cf44: malicious tar extraction can overwrite local files when external consumers call buildah/copier as non-root or on non-Linux systems. Users of Buildah itself are not affected. Fixed via commit a88128d47cb3f3fcbd9e874270c22271b73eb30d. The legacy github.com/containers/buildah/copier module has no patched versions; migrate to go.podman.io/buildah/copier.", "credit": "reporter: Oleh Konko / @1seal (alongside other reporters)", "classification": { "area": "authorization", "reason": "Tar extraction can overwrite files outside the intended destination; this is a filesystem access boundary, not a registry-pull defect.", "source": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "resolved_url": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "api_url": "https://api.github.com/repos/podman-container-tools/buildah/security-advisories/GHSA-3528-5p26-cf44", "state": "published", "ghsa_id": "GHSA-3528-5p26-cf44", "cve_id": "CVE-2026-79705", "summary": "Local file overwrite by extracting a malicious tar archive", "published_at": "2026-09-17T14:57:27Z", "updated_at": "2026-09-17T14:57:28Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-79705", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-79705", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-BUILDAH-SYMLINK-001/", "source_url": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2025-11395", "finding_id": "F-PODMAN-001-007", "repo": "podman-container-tools/container-libs", "url": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "patched": "go.podman.io/image/v5 5.39.3 / 5.41.2; go.podman.io/storage 1.62.1 / 1.64.1", "status": "patched", "kind": "cve", "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L", "note": "GHSA-3gcv-x57j-xqxv: malicious tar extraction can overwrite local files or change their attributes through podman load, oci-archive references, podman volume import, and storage/pkg/archive consumers. Registry image pulls are unaffected. Legacy github.com/containers/image/v5 and github.com/containers/storage modules have no patched versions; migrate to go.podman.io modules. Internal finding mapping is based on the reported volume-import path and shared archive extractor; the vendor advisory does not name internal finding IDs.", "credit": "reporter: Oleh Konko / @1seal (alongside other reporters)", "classification": { "area": "authorization", "reason": "Malicious archive entries can modify attacker-chosen local files during extraction; the affected boundary is filesystem access.", "source": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "resolved_url": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "api_url": "https://api.github.com/repos/podman-container-tools/container-libs/security-advisories/GHSA-3gcv-x57j-xqxv", "state": "published", "ghsa_id": "GHSA-3gcv-x57j-xqxv", "cve_id": "CVE-2025-11395", "summary": "Local file overwrite by extracting a malicious tar archive", "published_at": "2026-09-17T14:56:41Z", "updated_at": "2026-09-18T15:16:25Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2025-11395", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2025-11395", "fetched_at": "2026-09-23T20:30:40.966Z" }, "cvss": 6.1, "cvss_assessment": { "version": "3.1", "score": 6.1, "vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L", "assessor": "Container libraries (repository advisory)", "source_url": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "observed_at": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-PODMAN-001-007/", "source_url": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-65058", "title": "Trezor Safe improper security check in on-device display", "finding_id": "F-TREZOR-005", "repo": "trezor/trezor-firmware", "url": "https://www.cve.org/CVERecord?id=CVE-2026-65058", "patched": "Trezor Safe 3, Safe 5, and Safe 7 (commit 70c9b0c)", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N", "cwe": "CWE-358", "note": "on-device confirmation in Ethereum sign_tx and sign_tx_eip1559 covered only the initial calldata chunk while the signature committed to the full streamed calldata. CISA published CSAF VA-26-202-02 through cisagov/CSAF PR #436; fixed in commit 70c9b0c.", "credit": "Oleh Konko / 1seal", "cve_publication": { "id": "CVE-2026-65058", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-65058", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "Confirmation covers the initial calldata chunk rather than the complete signed stream.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-65058", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TREZOR-005/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-65058", "disclosed": null, "layer": "semantics" }, { "id": "CVE-2026-22703", "finding_id": "F-SIG-036-001", "repo": "sigstore/cosign", "url": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "patched": "cosign v2.6.2, v3.0.4", "status": "patched", "kind": "cve", "cvss": 5.5, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "resolved_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "api_url": "https://api.github.com/repos/sigstore/cosign/security-advisories/GHSA-whqx-f9j3-ch6m", "state": "published", "ghsa_id": "GHSA-whqx-f9j3-ch6m", "cve_id": "CVE-2026-22703", "summary": "Verification accepts any valid Rekor entry under certain conditions", "published_at": "2026-01-09T22:13:20Z", "updated_at": "2026-01-09T22:13:21Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-345" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-22703", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-22703", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "A valid log entry is accepted without the required binding to the verified object.", "source": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SIG-036-001/", "source_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-23831", "finding_id": "F-SIG-038-001", "repo": "sigstore/rekor", "url": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "patched": "rekor 1.5.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "resolved_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "api_url": "https://api.github.com/repos/sigstore/rekor/security-advisories/GHSA-273p-m2cw-6833", "state": "published", "ghsa_id": "GHSA-273p-m2cw-6833", "cve_id": "CVE-2026-23831", "summary": "COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message", "published_at": "2026-01-22T18:30:19Z", "updated_at": "2026-01-22T18:30:19Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-476" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-23831", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-23831", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "An empty COSE message reaches a nil dereference.", "source": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SIG-038-001/", "source_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-24117", "finding_id": "F-REKOR-SSRF-001", "repo": "sigstore/rekor", "url": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "patched": "rekor 1.5.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "resolved_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "api_url": "https://api.github.com/repos/sigstore/rekor/security-advisories/GHSA-4c4x-jm2x-pf9j", "state": "published", "ghsa_id": "GHSA-4c4x-jm2x-pf9j", "cve_id": "CVE-2026-24117", "summary": "Server-Side Request Forgery (SSRF) via provided public key URL", "published_at": "2026-01-22T18:30:51Z", "updated_at": "2026-01-22T18:30:52Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-918" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24117", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24117", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "The public-key URL controls an outbound request destination.", "source": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-REKOR-SSRF-001/", "source_url": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-24122", "finding_id": "F-COSIGN-001-003", "repo": "sigstore/cosign", "url": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "patched": "cosign 3.0.5", "status": "patched", "kind": "cve", "cvss": 3.7, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "resolved_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "api_url": "https://api.github.com/repos/sigstore/cosign/security-advisories/GHSA-wfqv-66vq-46rm", "state": "published", "ghsa_id": "GHSA-wfqv-66vq-46rm", "cve_id": "CVE-2026-24122", "summary": "Signatures considered valid with certificates that outlive expired CA certificates", "published_at": "2026-02-19T21:53:19Z", "updated_at": "2026-02-19T21:53:19Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-295" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24122", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24122", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Certificate validation does not enforce the issuing CA validity boundary.", "source": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-COSIGN-001-003/", "source_url": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-24137", "finding_id": "F-SIGSTORE-005", "repo": "sigstore/sigstore", "url": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "patched": "sigstore 1.10.4", "status": "patched", "kind": "cve", "cvss": 5.8, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "resolved_url": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "api_url": "https://api.github.com/repos/sigstore/sigstore/security-advisories/GHSA-fcv2-xgw5-pqxf", "state": "published", "ghsa_id": "GHSA-fcv2-xgw5-pqxf", "cve_id": "CVE-2026-24137", "summary": "Legacy TUF client allows for arbitrary file writes with target cache path traversal", "published_at": "2026-01-22T19:20:10Z", "updated_at": "2026-01-22T21:13:31Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24137", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24137", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A target name escapes the local cache directory.", "source": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SIGSTORE-005/", "source_url": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-48816", "finding_id": "F-SIG-JS-TLOGTIME-001", "repo": "sigstore/sigstore-js", "url": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "patched": "@sigstore/verify 3.1.1", "status": "patched", "kind": "cve", "cvss": 6.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "cwe": "CWE-345", "note": "GHSA-xgjw-pm74-86q4; inclusionProof-only bundle integratedTime was treated as a trusted timestamp without cryptographic binding.", "credit": "reporter: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "resolved_url": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "api_url": "https://api.github.com/repos/sigstore/sigstore-js/security-advisories/GHSA-xgjw-pm74-86q4", "state": "published", "ghsa_id": "GHSA-xgjw-pm74-86q4", "cve_id": "CVE-2026-48816", "summary": "Insufficient Verification of Data Authenticity in sigstore-js", "published_at": "2026-05-27T16:23:30Z", "updated_at": "2026-05-27T19:24:03Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-345" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-48816", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-48816", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "An unauthenticated integratedTime is used as trusted time evidence; the affected property is integrity of the timestamp used for verification.", "source": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SIG-JS-TLOGTIME-001/", "source_url": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "title": null, "disclosed": null, "layer": "integrity" }, { "id": "CVE-2026-23991", "finding_id": "F-TUF-003", "repo": "theupdateframework/go-tuf/v2", "url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "patched": "go-tuf/v2 2.3.1", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "resolved_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "api_url": "https://api.github.com/repos/theupdateframework/go-tuf/security-advisories/GHSA-846p-jg2w-w324", "state": "published", "ghsa_id": "GHSA-846p-jg2w-w324", "cve_id": "CVE-2026-23991", "summary": "Client DoS via malformed server response", "published_at": "2026-01-20T14:47:06Z", "updated_at": "2026-01-20T22:55:19Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-617", "CWE-754" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-23991", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-23991", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Malformed repository input reaches an assertion failure.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TUF-003/", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-23992", "finding_id": "F-TUF-001", "repo": "theupdateframework/go-tuf/v2", "url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "patched": "go-tuf/v2 2.3.1", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "resolved_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "api_url": "https://api.github.com/repos/theupdateframework/go-tuf/security-advisories/GHSA-fphv-w9fq-2525", "state": "published", "ghsa_id": "GHSA-fphv-w9fq-2525", "cve_id": "CVE-2026-23992", "summary": "Improper validation of configured threshold for delegations", "published_at": "2026-01-20T14:50:24Z", "updated_at": "2026-01-20T22:56:14Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-347" ], "credits": [ { "login": "1seal", "role": "remediation_reviewer", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-23992", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-23992", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "The delegated role can be accepted without the configured number of authorized signatures; this weakens the metadata authorization policy.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TUF-001/", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-24686", "finding_id": "F-TUF-008", "repo": "theupdateframework/go-tuf/v2", "url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "patched": "go-tuf/v2 2.4.1", "status": "patched", "kind": "cve", "cvss": 8.1, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "resolved_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "api_url": "https://api.github.com/repos/theupdateframework/go-tuf/security-advisories/GHSA-jqc5-w2xx-5vq4", "state": "published", "ghsa_id": "GHSA-jqc5-w2xx-5vq4", "cve_id": "CVE-2026-24686", "summary": "go-tuf TAP 4 multirepo repoName path traversal escapes local metadata cache directory", "published_at": "2026-01-26T12:46:25Z", "updated_at": "2026-01-26T20:53:24Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24686", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24686", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A repository name crosses the intended cache-path boundary.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TUF-008/", "source_url": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-24845", "finding_id": "F-MALCONTENT-003", "repo": "chainguard-dev/malcontent", "url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "patched": "malcontent 1.20.3", "status": "patched", "kind": "cve", "cvss": 6.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "resolved_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "api_url": "https://api.github.com/repos/chainguard-dev/malcontent/security-advisories/GHSA-9m43-p3cx-w8j5", "state": "published", "ghsa_id": "GHSA-9m43-p3cx-w8j5", "cve_id": "CVE-2026-24845", "summary": "OCI image scanning could expose registry credentials", "published_at": "2026-01-29T16:06:45Z", "updated_at": "2026-01-29T16:06:45Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-522" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24845", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24845", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "confidentiality", "reason": "The advisory describes exposure of registry credentials during OCI scanning.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-003/", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "title": null, "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "id": "CVE-2026-24846", "finding_id": "F-MALCONTENT-001", "repo": "chainguard-dev/malcontent", "url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "patched": "malcontent 1.20.3", "status": "patched", "kind": "cve", "cvss": 5.5, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "resolved_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "api_url": "https://api.github.com/repos/chainguard-dev/malcontent/security-advisories/GHSA-923j-vrcg-hxwh", "state": "published", "ghsa_id": "GHSA-923j-vrcg-hxwh", "cve_id": "CVE-2026-24846", "summary": "Archive extraction could write outside extraction directory", "published_at": "2026-01-29T16:06:43Z", "updated_at": "2026-01-29T16:06:43Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22", "CWE-683" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24846", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24846", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Archive extraction escapes its intended directory.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-001/", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-25121", "finding_id": "F-APKO-001", "repo": "chainguard-dev/apko", "url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "patched": "apko (commit d8b7887)", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "resolved_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "api_url": "https://api.github.com/repos/chainguard-dev/apko/security-advisories/GHSA-5g94-c2wx-8pxw", "state": "published", "ghsa_id": "GHSA-5g94-c2wx-8pxw", "cve_id": "CVE-2026-25121", "summary": "Path traversal in apko dirFS allows filesystem writes outside base", "published_at": "2026-02-03T21:21:24Z", "updated_at": "2026-02-03T21:21:25Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-23" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25121", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25121", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Filesystem operations escape the directory-backed root.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-001/", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-25140", "finding_id": "F-APKO-007", "repo": "chainguard-dev/apko", "url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "patched": "apko (commit 2be3903)", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "resolved_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "api_url": "https://api.github.com/repos/chainguard-dev/apko/security-advisories/GHSA-f4w5-5xv9-85f6", "state": "published", "ghsa_id": "GHSA-f4w5-5xv9-85f6", "cve_id": "CVE-2026-25140", "summary": "potential unbounded resource consumption in expandapk.ExpandApk on attacker-controlled .apk streams", "published_at": "2026-02-03T21:21:08Z", "updated_at": "2026-02-03T21:21:08Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-400" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25140", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25140", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "APK expansion lacks an effective output-size bound.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-007/", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-25122", "finding_id": "F-APKO-003", "repo": "chainguard-dev/apko", "url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "patched": "apko v1.1.0", "status": "patched", "kind": "cve", "note": "unbounded resource consumption in expandapk.Split", "credit": "reporter: @1seal", "cvss": 5.5, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "resolved_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "api_url": "https://api.github.com/repos/chainguard-dev/apko/security-advisories/GHSA-6p9p-q6wh-9j89", "state": "published", "ghsa_id": "GHSA-6p9p-q6wh-9j89", "cve_id": "CVE-2026-25122", "summary": "unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams ", "published_at": "2026-02-03T21:20:45Z", "updated_at": "2026-02-03T21:20:45Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-400" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25122", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25122", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Archive splitting permits unbounded resource consumption.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-003/", "source_url": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-42574", "title": "apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root", "finding_id": "F-APKO-SYMLINK-001", "repo": "chainguard-dev/apko", "url": "https://github.com/advisories/GHSA-qq3r-w4hj-gjp6", "patched": "apko v1.2.5", "status": "patched", "kind": "cve", "note": "symlink-following path traversal in apko dirFS allows multiple entry points to escape the build root", "credit": "reporter: @1seal", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "cve_publication": { "id": "CVE-2026-42574", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-42574", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Symlink traversal defeats filesystem containment.", "source": "https://github.com/advisories/GHSA-qq3r-w4hj-gjp6", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-SYMLINK-001/", "source_url": "https://github.com/advisories/GHSA-qq3r-w4hj-gjp6", "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-42576", "title": "apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery", "finding_id": "F-APKO-002", "repo": "chainguard-dev/apko", "url": "https://github.com/advisories/GHSA-m7hm-vm4x-28jf", "patched": "apko v1.2.7", "status": "patched", "kind": "cve", "note": "panic on non-RSA JWKS key in apko DiscoverKeys causes crash during key discovery", "credit": "reporter: @1seal", "cvss": 6.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "cve_publication": { "id": "CVE-2026-42576", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-42576", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "An unexpected JWKS key type triggers a panic.", "source": "https://github.com/advisories/GHSA-m7hm-vm4x-28jf", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-002/", "source_url": "https://github.com/advisories/GHSA-m7hm-vm4x-28jf", "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-42575", "title": "apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)", "finding_id": "F-APKO-CHECKSUM-001", "repo": "chainguard-dev/apko", "url": "https://github.com/advisories/GHSA-hcwr-pq9g-rq3m", "patched": "apko v1.2.7", "status": "patched", "kind": "cve", "note": "downloaded APK packages are not verified against APKINDEX checksum (package substitution possible)", "credit": "reporter: @1seal", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "cve_publication": { "id": "CVE-2026-42575", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-42575", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "Package checksums are not enforced on the affected path.", "source": "https://github.com/advisories/GHSA-hcwr-pq9g-rq3m", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-APKO-CHECKSUM-001/", "source_url": "https://github.com/advisories/GHSA-hcwr-pq9g-rq3m", "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-3833", "title": "Gnutls: gnutls: policy bypass due to case-sensitive nameconstraints comparison", "finding_id": "F-GNUTLS-NAMECONSTRAINTS-001", "repo": "gnutls/gnutls", "url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "patched": "GnuTLS 3.8.13", "status": "patched", "kind": "cve", "note": "x509/name-constraints: compare domain names case-insensitive", "credit": "independently reported by Oleh Konko (1seal) and Joshua Rogers", "cve_publication": { "id": "CVE-2026-3833", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-3833", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Case-sensitive DNS comparison bypasses certificate name constraints.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-GNUTLS-NAMECONSTRAINTS-001/", "source_url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-3832", "title": "Gnutls: gnutls: security bypass allows acceptance of revoked server certificates via crafted ocsp response", "finding_id": "F-GNUTLS-OCSP-001", "repo": "gnutls/gnutls", "url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "patched": "GnuTLS 3.8.13", "status": "patched", "kind": "cve", "note": "cert-session: fix multi-entry OCSP revocation bypass", "credit": "independently reported by Oleh Konko (1seal) and Joshua Rogers", "cve_publication": { "id": "CVE-2026-3832", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-3832", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Multi-entry OCSP processing can miss a revoked status.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-GNUTLS-OCSP-001/", "source_url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-42012", "title": "Gnutls: gnutls: certificate validation bypass due to improper handling of uri and srv sans", "finding_id": "F-GNUTLS-HOSTNAME-001", "repo": "gnutls/gnutls", "url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "patched": "GnuTLS 3.8.13", "status": "patched", "kind": "cve", "note": "x509/hostname-verify: make URI/SRV SAN preclude CN fallback", "credit": "reported by Oleh Konko (1seal)", "cve_publication": { "id": "CVE-2026-42012", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-42012", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "URI or SRV SAN entries incorrectly permit common-name fallback.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-GNUTLS-HOSTNAME-001/", "source_url": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-24844", "finding_id": "F-MELANGE-001", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "patched": "melange (commit e51ca30c)", "status": "patched", "kind": "cve", "cvss": 7.9, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-vqqr-rmpc-hhg2", "state": "published", "ghsa_id": "GHSA-vqqr-rmpc-hhg2", "cve_id": "CVE-2026-24844", "summary": "Pipeline working-directory could allow command injection", "published_at": "2026-02-03T21:21:35Z", "updated_at": "2026-02-03T21:21:36Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-78" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24844", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24844", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "Working-directory handling reaches command execution.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-001/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "CVE-2026-24843", "finding_id": "F-MELANGE-005", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "patched": "melange (commit 6e243d0d)", "status": "patched", "kind": "cve", "cvss": 8.2, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-qxx2-7h4c-83f4", "state": "published", "ghsa_id": "GHSA-qxx2-7h4c-83f4", "cve_id": "CVE-2026-24843", "summary": "QEMU runner could write files outside workspace directory", "published_at": "2026-02-03T21:23:00Z", "updated_at": "2026-02-03T21:23:00Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-24843", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-24843", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "QEMU runner path handling permits an escape.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-005/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-25143", "finding_id": "F-MELANGE-007", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "patched": "melange (commit bd132535)", "status": "patched", "kind": "cve", "cvss": 7.8, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-rf4g-89h5-crcr", "state": "published", "ghsa_id": "GHSA-rf4g-89h5-crcr", "cve_id": "CVE-2026-25143", "summary": "potential host command execution via license-check YAML mode patch pipeline ", "published_at": "2026-02-03T21:22:31Z", "updated_at": "2026-02-03T21:22:32Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-78" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25143", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25143", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "License metadata can reach host command interpretation.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-007/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "CVE-2026-25145", "finding_id": "F-MELANGE-006", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "patched": "melange (commit 2f95c9f)", "status": "patched", "kind": "cve", "cvss": 5.5, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-2w4f-9fgg-q2v9", "state": "published", "ghsa_id": "GHSA-2w4f-9fgg-q2v9", "cve_id": "CVE-2026-25145", "summary": "path traversal in `license-path` allows reading files outside workspace ", "published_at": "2026-02-03T21:22:04Z", "updated_at": "2026-02-03T21:22:04Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22", "CWE-200" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25145", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25145", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "License file resolution reads outside the intended root.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-006/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-25518", "finding_id": "F-CERTMGR-DNS-001", "repo": "cert-manager/cert-manager", "url": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "patched": "cert-manager v1.18.5, v1.19.3", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "resolved_url": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "api_url": "https://api.github.com/repos/cert-manager/cert-manager/security-advisories/GHSA-gx3x-vq4p-mhhv", "state": "published", "ghsa_id": "GHSA-gx3x-vq4p-mhhv", "cve_id": "CVE-2026-25518", "summary": "cert-manager-controller DoS via Specially Crafted DNS Response", "published_at": "2026-02-02T16:25:33Z", "updated_at": "2026-02-03T00:51:25Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-129", "CWE-704" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-25518", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25518", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Malformed DNS response fields reach a panic.", "source": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-CERTMGR-DNS-001/", "source_url": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-26189", "finding_id": "F-TRIVY-ACTION-001", "repo": "aquasecurity/trivy-action", "url": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "patched": "trivy-action >= 0.34.0", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "resolved_url": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "api_url": "https://api.github.com/repos/aquasecurity/trivy-action/security-advisories/GHSA-9p44-j4g5-cfx5", "state": "published", "ghsa_id": "GHSA-9p44-j4g5-cfx5", "cve_id": "CVE-2026-26189", "summary": "script injection via sourced env file in composite action", "published_at": "2026-02-18T05:47:51Z", "updated_at": "2026-02-20T23:37:46Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-78" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-26189", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-26189", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "Untrusted environment content is sourced as shell code.", "source": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TRIVY-ACTION-001/", "source_url": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "CVE-2026-27589", "finding_id": "F-CADDY-ADMIN-LOAD-001", "repo": "caddyserver/caddy", "url": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "patched": "caddy v2.11.0", "status": "patched", "kind": "cve", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "resolved_url": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "api_url": "https://api.github.com/repos/caddyserver/caddy/security-advisories/GHSA-879p-475x-rqh2", "state": "published", "ghsa_id": "GHSA-879p-475x-rqh2", "cve_id": "CVE-2026-27589", "summary": "cross-origin config application via local admin API /load (caddy)", "published_at": "2026-02-23T04:22:19Z", "updated_at": "2026-02-23T04:22:19Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-352" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-27589", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-27589", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Cross-origin requests reach the administrative configuration interface.", "source": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-CADDY-ADMIN-LOAD-001/", "source_url": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-22728", "finding_id": "F-SEALED-SECRETS-ROTATE-SCOPE-001", "repo": "bitnami-labs/sealed-secrets", "url": "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "patched": "sealed-secrets v0.36.0", "status": "patched", "kind": "cve", "cvss": 4.9, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N", "classification": { "area": "authorization", "reason": "Rotation can widen a sealed secret from its original name/namespace scope to cluster-wide access.", "source": "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "resolved_url": "https://github.com/bitnami/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "api_url": "https://api.github.com/repos/bitnami/sealed-secrets/security-advisories/GHSA-465p-v42x-3fmj", "state": "published", "ghsa_id": "GHSA-465p-v42x-3fmj", "cve_id": "CVE-2026-22728", "summary": "sealed-secrets /v1/rotate can widen sealing scope to cluster-wide via attacker-controlled template annotations", "published_at": "2026-02-25T17:54:01Z", "updated_at": "2026-02-25T17:54:01Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-284" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-22728", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-22728", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SEALED-SECRETS-ROTATE-SCOPE-001/", "source_url": "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-29054", "finding_id": "F-TRAEFIK-003", "repo": "traefik/traefik", "url": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "patched": "Traefik: v2.11.38; Traefik: v3.6.9", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "resolved_url": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "api_url": "https://api.github.com/repos/traefik/traefik/security-advisories/GHSA-92mv-8f8w-wq52", "state": "published", "ghsa_id": "GHSA-92mv-8f8w-wq52", "cve_id": "CVE-2026-29054", "summary": "Case-Sensitive Bypass in Connection Header Allows Removal of X-Forwarded Headers", "published_at": "2026-03-04T13:10:10Z", "updated_at": "2026-03-04T13:10:10Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-178" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "Traefik", "ecosystem": "go", "affected": ">= v2.11.9, <= v2.11.37", "patched": "v2.11.38" }, { "name": "Traefik", "ecosystem": "go", "affected": ">= v3.1.3, <= v3.6.8", "patched": "v3.6.9" } ] }, "cve_publication": { "id": "CVE-2026-29054", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29054", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "Case-dependent Connection header processing gives inconsistent meaning to forwarded-header removal, a request-interpretation boundary.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TRAEFIK-003/", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "CVE-2026-26999", "finding_id": "F-TRAEFIK-004", "repo": "traefik/traefik", "url": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "patched": "Traefik: v2.11.38; Traefik: v3.6.9", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "resolved_url": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "api_url": "https://api.github.com/repos/traefik/traefik/security-advisories/GHSA-xw98-5q62-jx94", "state": "published", "ghsa_id": "GHSA-xw98-5q62-jx94", "cve_id": "CVE-2026-26999", "summary": "TLS Handshake Error Handling Allows Stalled Connections on TCP Routers", "published_at": "2026-03-04T13:10:46Z", "updated_at": "2026-03-04T13:10:46Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-400" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "Traefik", "ecosystem": "go", "affected": "<= v2.11.37", "patched": "v2.11.38" }, { "name": "Traefik", "ecosystem": "go", "affected": "<= v3.6.8 ", "patched": "v3.6.9" } ] }, "cve_publication": { "id": "CVE-2026-26999", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-26999", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Incomplete TCP handshakes retain resources without an effective bound.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TRAEFIK-004/", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-29777", "finding_id": "F-TRAEFIK-006", "repo": "traefik/traefik", "url": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "patched": "v3.6.10", "status": "patched", "kind": "cve", "cvss": 8.7, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "resolved_url": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "api_url": "https://api.github.com/repos/traefik/traefik/security-advisories/GHSA-8q2w-wr49-whqj", "state": "published", "ghsa_id": "GHSA-8q2w-wr49-whqj", "cve_id": "CVE-2026-29777", "summary": "Kubernetes gateway rule injection via unescaped backticks in HTTPRoute match values", "published_at": "2026-03-11T11:29:40Z", "updated_at": "2026-03-11T11:29:40Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-74" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-29777", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29777", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "semantics", "reason": "Backticks in rule data change rule-expression interpretation.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TRAEFIK-006/", "source_url": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "GHSA-3jrg-j22w-mpmc", "finding_ids": [ "F-AWS-LC-NAMECONSTRAINTS-001", "F-AWS-LC-NAMECONSTRAINTS-002" ], "repo": "aws/aws-lc", "url": "https://github.com/aws/aws-lc/security/advisories/GHSA-3jrg-j22w-mpmc", "patched": "AWS-LC 1.71.0", "severity": "moderate", "source_reviewed": "2026-09-25", "status": "patched", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": null, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/aws/aws-lc/security/advisories/GHSA-3jrg-j22w-mpmc", "resolved_url": "https://github.com/aws/aws-lc/security/advisories/GHSA-3jrg-j22w-mpmc", "api_url": "https://api.github.com/repos/aws/aws-lc/security-advisories/GHSA-3jrg-j22w-mpmc", "state": "published", "ghsa_id": "GHSA-3jrg-j22w-mpmc", "cve_id": null, "summary": "AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN", "published_at": "2026-03-19T20:46:26Z", "updated_at": "2026-03-19T20:46:26Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "classification": { "area": "identity", "reason": "Wildcard common names bypass name-constraint enforcement. Unicode common names are skipped by name-constraint enforcement.", "source": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-AWS-LC-NAMECONSTRAINTS-001/", "source_url": "https://github.com/aws/aws-lc/security/advisories/GHSA-3jrg-j22w-mpmc", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "GHSA-394x-vwmw-crm3", "finding_ids": [ "F-AWS-LC-NAMECONSTRAINTS-001", "F-AWS-LC-NAMECONSTRAINTS-002" ], "repo": "aws/aws-lc-rs", "url": "https://github.com/aws/aws-lc-rs/security/advisories/GHSA-394x-vwmw-crm3", "patched": "aws-lc-sys 0.39.0", "severity": "moderate", "source_reviewed": "2026-09-25", "status": "patched", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": null, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/aws/aws-lc-rs/security/advisories/GHSA-394x-vwmw-crm3", "resolved_url": "https://github.com/aws/aws-lc-rs/security/advisories/GHSA-394x-vwmw-crm3", "api_url": "https://api.github.com/repos/aws/aws-lc-rs/security-advisories/GHSA-394x-vwmw-crm3", "state": "published", "ghsa_id": "GHSA-394x-vwmw-crm3", "cve_id": null, "summary": "AWS-LC X.509 Name Constraints Bypass via Wildcard/Unicode CN", "published_at": "2026-03-19T20:46:40Z", "updated_at": "2026-03-19T20:46:40Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "classification": { "area": "identity", "reason": "Wildcard common names bypass name-constraint enforcement. Unicode common names are skipped by name-constraint enforcement.", "source": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-AWS-LC-NAMECONSTRAINTS-001/", "source_url": "https://github.com/aws/aws-lc-rs/security/advisories/GHSA-394x-vwmw-crm3", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "GHSA-x4cm-pcq4-39j4", "finding_id": "F-MOZILLA-SOPS-002", "repo": "getsops/sops", "url": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "patched": "sops 3.13.0", "status": "patched", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": null, "note": "exec-file --filename rejects non-local paths so decrypted plaintext cannot escape the temporary-directory cleanup boundary; fixed via PR #2155.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "resolved_url": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "api_url": "https://api.github.com/repos/getsops/sops/security-advisories/GHSA-x4cm-pcq4-39j4", "state": "published", "ghsa_id": "GHSA-x4cm-pcq4-39j4", "cve_id": null, "summary": "Path traversal in `sops exec-file --filename` leaks decrypted plaintext outside temporary directory", "published_at": "2026-08-14T09:19:15Z", "updated_at": "2026-08-14T09:19:15Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "classification": { "area": "confidentiality", "reason": "Decrypted plaintext can remain outside the temporary directory and its cleanup, exposing secret content to later readers.", "source": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "reviewed": "2026-09-24" }, "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-MOZILLA-SOPS-002/", "source_url": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "title": null, "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "id": "GHSA-jgf3-f6rg-8x3h", "finding_id": "F-MOZILLA-SOPS-004", "repo": "getsops/sops", "url": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "patched": null, "status": "mitigation available; configuration required", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": null, "note": "SOPS 3.13.0 adds SOPS_HC_VAULT_ALLOWLIST via PR #2164. Its default remains all, preserving unrestricted forwarding; set it to none or a restrictive list of trusted Vault/OpenBao endpoints to mitigate token exfiltration through untrusted encrypted-file metadata.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "resolved_url": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "api_url": "https://api.github.com/repos/getsops/sops/security-advisories/GHSA-jgf3-f6rg-8x3h", "state": "published", "ghsa_id": "GHSA-jgf3-f6rg-8x3h", "cve_id": null, "summary": "HC Vault / OpenBao token exfiltration when decrypting untrusted SOPS-encrypted files", "published_at": "2026-08-14T09:18:23Z", "updated_at": "2026-08-14T09:18:23Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-522", "CWE-918" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "classification": { "area": "authorization", "reason": "Untrusted Vault metadata chooses the destination receiving a local token.", "source": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "reviewed": "2026-09-24" }, "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-MOZILLA-SOPS-004/", "source_url": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "GHSA-vhvq-fv9f-wh4q", "finding_id": "F-AUTHZED-SPICEDB-001", "repo": "authzed/spicedb", "url": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "patched": "spicedb v1.49.1", "status": "patched", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": null, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "resolved_url": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "api_url": "https://api.github.com/repos/authzed/spicedb/security-advisories/GHSA-vhvq-fv9f-wh4q", "state": "published", "ghsa_id": "GHSA-vhvq-fv9f-wh4q", "cve_id": null, "summary": "LookupResources Cursor section tampering can crash SpiceDB process via tuple.MustParse panic", "published_at": "2026-02-06T21:21:13Z", "updated_at": "2026-02-06T21:21:13Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-248" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "classification": { "area": "availability", "reason": "Untrusted cursor parsing reaches a MustParse panic.", "source": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-AUTHZED-SPICEDB-001/", "source_url": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-93602", "finding_id": "F-RUSTLS-WEBPKI-001", "repo": "rustls/webpki", "url": "https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4", "patched": "0.104.0-alpha.5, 0.103.10", "status": "patched", "kind": "cve", "cve": "CVE-2026-93602", "cvss": 4.4, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4", "resolved_url": "https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4", "api_url": "https://api.github.com/repos/rustls/webpki/security-advisories/GHSA-pwjx-qhcg-rvj4", "state": "published", "ghsa_id": "GHSA-pwjx-qhcg-rvj4", "cve_id": null, "summary": "CRLs not considered authoritative by Distribution Point due to faulty matching logic", "published_at": "2026-03-20T21:20:38Z", "updated_at": "2026-03-23T15:00:59Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-299" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "ghsa": "GHSA-pwjx-qhcg-rvj4", "note": "CVE-2026-93602: VulnCheck CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-18. Assigned by VulnCheck; the repository GHSA snapshot still has no CVE identifier.", "cve_publication": { "id": "CVE-2026-93602", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-93602", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "CRL authority matching is incomplete.", "source": "https://github.com/rustls/webpki/pull/469", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-RUSTLS-WEBPKI-001/", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-pwjx-qhcg-rvj4", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-93600", "finding_id": "F-RUSTLS-WEBPKI-NAMECONSTRAINTS-URI-001", "repo": "rustls/webpki", "url": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "patched": ">= 0.103.12, >= 0.104.0-alpha.6", "status": "patched", "kind": "cve", "cve": "CVE-2026-93600", "cvss": 2.2, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N", "credit": "reporter: @1seal", "note": "Name constraints for URI names were incorrectly accepted. CVE-2026-93600: VulnCheck CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-18. Assigned by VulnCheck; the repository GHSA snapshot still has no CVE identifier.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "resolved_url": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "api_url": "https://api.github.com/repos/rustls/webpki/security-advisories/GHSA-965h-392x-2mh5", "state": "published", "ghsa_id": "GHSA-965h-392x-2mh5", "cve_id": null, "summary": "Name constraints for URI names were incorrectly accepted", "published_at": "2026-04-15T14:24:06Z", "updated_at": "2026-04-15T14:24:07Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-295" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "ghsa": "GHSA-965h-392x-2mh5", "cve_publication": { "id": "CVE-2026-93600", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-93600", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "URI name constraints are not enforced as required.", "source": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-RUSTLS-WEBPKI-NAMECONSTRAINTS-URI-001/", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-93601", "finding_id": "F-RUSTLS-WEBPKI-NAMECONSTRAINTS-WILDCARD-001", "repo": "rustls/webpki", "url": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "patched": ">= 0.103.12, >= 0.104.0-alpha.6", "status": "patched", "kind": "cve", "cve": "CVE-2026-93601", "cvss": 2.2, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N", "credit": "reporter: @1seal", "note": "Name constraints were accepted for certificates asserting a wildcard name. CVE-2026-93601: VulnCheck CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-18. Assigned by VulnCheck; the repository GHSA snapshot still has no CVE identifier.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "resolved_url": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "api_url": "https://api.github.com/repos/rustls/webpki/security-advisories/GHSA-xgp8-3hg3-c2mh", "state": "published", "ghsa_id": "GHSA-xgp8-3hg3-c2mh", "cve_id": null, "summary": "Name constraints were accepted for certificates asserting a wildcard name", "published_at": "2026-04-15T14:24:14Z", "updated_at": "2026-04-15T14:24:14Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-295" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "ghsa": "GHSA-xgp8-3hg3-c2mh", "cve_publication": { "id": "CVE-2026-93601", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-93601", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Wildcard DNS names bypass constraint checks.", "source": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-RUSTLS-WEBPKI-NAMECONSTRAINTS-WILDCARD-001/", "source_url": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-35468", "finding_id": "F-NIMIQ-HISTORYINDEX-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "patched": "nimiq-blockchain v1.3.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "GHSA-xr78-2jhh-9wf9; patched in v1.3.0 via PR #3667", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-xr78-2jhh-9wf9", "state": "published", "ghsa_id": "GHSA-xr78-2jhh-9wf9", "cve_id": "CVE-2026-35468", "summary": "Panic in history index request handlers when a full node runs without the history index", "published_at": "2026-04-02T22:07:38Z", "updated_at": "2026-04-03T02:17:40Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-252" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-35468", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-35468", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "History index input reaches a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-HISTORYINDEX-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-40094", "finding_id": "F-NIMIQ-DISCOVERY-EMPTY-ADDRLIST-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "patched": "nimiq-network-libp2p v1.4.0", "status": "patched", "kind": "cve", "cvss": 4.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L", "note": "GHSA-c45m-6x25-3cjq; patched in v1.4.0 via PR #3715", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-c45m-6x25-3cjq", "state": "published", "ghsa_id": "GHSA-c45m-6x25-3cjq", "cve_id": "CVE-2026-40094", "summary": "Untrusted peer can crash address book via empty peer contact addresses", "published_at": "2026-05-15T04:18:45Z", "updated_at": "2026-05-15T04:18:45Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-754" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-40094", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-40094", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "An empty discovery address list reaches a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-DISCOVERY-EMPTY-ADDRLIST-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-44505", "finding_id": "F-NIMIQ-DHTGET-HANG-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "patched": "network-libp2p v1.4.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "GHSA-g39c-jcgg-qwvr; patched in v1.4.0 via PR #3716", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-g39c-jcgg-qwvr", "state": "published", "ghsa_id": "GHSA-g39c-jcgg-qwvr", "cve_id": "CVE-2026-44505", "summary": "Untrusted peer can wedge DHT", "published_at": "2026-05-15T03:58:04Z", "updated_at": "2026-05-15T03:58:04Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-755" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-44505", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-44505", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "DHT query completion can remain stalled.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-DHTGET-HANG-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34063", "finding_id": "F-NIMIQ-DISCOVERY-DOUBLE-SUBSTREAM-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "patched": "network-libp2p v1.3.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-74hp-mhfx-m45h; patched in v1.3.0 via PR #3666 / release v1.3.0", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-74hp-mhfx-m45h", "state": "published", "ghsa_id": "GHSA-74hp-mhfx-m45h", "cve_id": "CVE-2026-34063", "summary": "Peer can crash the node by opening discovery protocol substream twice", "published_at": "2026-04-22T01:25:26Z", "updated_at": "2026-04-22T01:25:26Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-617" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34063", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34063", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "A repeated discovery substream violates an assumed state and panics.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-DISCOVERY-DOUBLE-SUBSTREAM-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34062", "finding_id": "F-NIMIQ-REQRES-STREAMS-STALL-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "patched": "network-libp2p v1.3.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "GHSA-gh7r-qh4p-q4fr; patched in v1.3.0 via PR #3663", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-gh7r-qh4p-q4fr", "state": "published", "ghsa_id": "GHSA-gh7r-qh4p-q4fr", "cve_id": "CVE-2026-34062", "summary": "nimiq-libp2p request/response codec reads entire stream before size validation", "published_at": "2026-04-22T01:29:52Z", "updated_at": "2026-04-22T01:29:52Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-770" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34062", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34062", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Request/response streams can remain blocked without an effective limit.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-REQRES-STREAMS-STALL-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-9064", "title": "389-ds-base: 389-ds-base: unbounded ldap controls count in get_ldapmessage_controls_ext() causes cpu and heap amplification (remote dos)", "finding_id": "F-FREEIPA-389DS-001", "repo": "389ds/389-ds-base", "url": "https://access.redhat.com/security/cve/cve-2026-9064", "status": "affected", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "cwe": "CWE-770", "credit": "Red Hat acknowledgement: Oleh Konko (1seal.org)", "note": "389-ds-base get_ldapmessage_controls_ext() unbounded LDAP controls count; remote unauthenticated CPU and heap amplification DoS.", "classification": { "area": "availability", "reason": "Excessive LDAP control counts amplify CPU work and heap allocation, exhausting directory-service resources.", "source": "https://access.redhat.com/security/cve/cve-2026-9064", "reviewed": "2026-09-21" }, "cve_publication": { "id": "CVE-2026-9064", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-9064", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-FREEIPA-389DS-001/", "source_url": "https://access.redhat.com/security/cve/cve-2026-9064", "disclosed": null, "layer": "availability" }, { "id": "GHSA-w5f8-87h2-m573", "finding_id": "F-NIMIQ-REQRES-INBOUNDLEAK-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "patched": "nimiq-network-libp2p v1.3.0", "status": "patched", "kind": "ghsa", "cve": null, "cvss": 0, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "note": "GHSA-w5f8-87h2-m573; patched in v1.3.0 via PR #3665", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-w5f8-87h2-m573", "state": "published", "ghsa_id": "GHSA-w5f8-87h2-m573", "cve_id": null, "summary": "Request/Response inbound failure retains stale `response_channels` state after attacker-controlled failed requests", "published_at": "2026-04-02T22:13:03Z", "updated_at": "2026-04-02T22:13:03Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-772" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "classification": { "area": "availability", "reason": "Inbound request channels retain resources after their useful lifetime.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-REQRES-INBOUNDLEAK-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "GHSA-hj3g-hh5f-63mp", "finding_id": "F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "patched": "v1.3.0", "status": "patched", "kind": "ghsa", "cve": null, "cvss": null, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-hj3g-hh5f-63mp", "state": "published", "ghsa_id": "GHSA-hj3g-hh5f-63mp", "cve_id": null, "summary": "Discovery peer contact book poisoning via future timestamps ", "published_at": "2026-04-22T00:58:35Z", "updated_at": "2026-04-22T00:58:35Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-345", "CWE-1284" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "classification": { "area": "integrity", "reason": "Unchecked future timestamps can poison the peer contact book, compromising the integrity of stored discovery state.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-46539", "finding_id": "F-NIMIQ-BLOCKINCLUSIONPROOF-INTERLINK-HOPS-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "patched": "nimiq-primitives v1.4.0", "status": "patched", "kind": "cve", "cve": "CVE-2026-46539", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N", "credit": "finder: @1seal", "note": "BlockInclusionProof::is_block_proven accepted an empty interlink-hop proof path without cryptographic verification. CVE-2026-46539: GitHub_M CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-06-09.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-799f-29jm-gr6c", "state": "published", "ghsa_id": "GHSA-799f-29jm-gr6c", "cve_id": "CVE-2026-46539", "summary": "BlockInclusionProof interlink issue when hops are empty", "published_at": "2026-05-15T04:02:20Z", "updated_at": "2026-05-15T19:37:07Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-345" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "ghsa": "GHSA-799f-29jm-gr6c", "cve_publication": { "id": "CVE-2026-46539", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-46539", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "An empty or incomplete inclusion path can satisfy proof verification.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-BLOCKINCLUSIONPROOF-INTERLINK-HOPS-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-33747", "finding_id": "F-BUILDKIT-001-001", "repo": "moby/buildkit", "url": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "patched": "v0.28.1+", "status": "patched", "kind": "cve", "cvss": 8.4, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "resolved_url": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "api_url": "https://api.github.com/repos/moby/buildkit/security-advisories/GHSA-4c29-8rgm-jvjj", "state": "published", "ghsa_id": "GHSA-4c29-8rgm-jvjj", "cve_id": "CVE-2026-33747", "summary": "Malicious frontend can cause file escape outside of storage root", "published_at": "2026-03-25T15:10:57Z", "updated_at": "2026-03-25T15:10:57Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-33747", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33747", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "ContainerID traversal escapes the executor root.", "source": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-BUILDKIT-001-001/", "source_url": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-34073", "finding_id": "F-PYCA-CRYPTOGRAPHY-NAMECONSTRAINTS-WILDCARD-001", "repo": "pyca/cryptography", "url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "patched": ">= 46.0.6", "status": "patched", "kind": "cve", "cvss": null, "cvss_vector": null, "credit": "Reporter: 1seal", "note": "inferred mapping", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "resolved_url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "api_url": "https://api.github.com/repos/pyca/cryptography/security-advisories/GHSA-m959-cc7f-wv43", "state": "published", "ghsa_id": "GHSA-m959-cc7f-wv43", "cve_id": "CVE-2026-34073", "summary": "X.509: bypass of name constraints on wildcard SANs with matching peer names", "published_at": "2026-03-25T23:27:02Z", "updated_at": "2026-03-25T23:27:02Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-295" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34073", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34073", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Wildcard DNS names bypass certificate name constraints.", "source": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-PYCA-CRYPTOGRAPHY-NAMECONSTRAINTS-WILDCARD-001/", "source_url": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-28457", "finding_id": "F-OPENCLAW-001", "repo": "openclaw/openclaw", "url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "patched": "openclaw >= 2026.2.14", "status": "patched", "kind": "cve", "cvss": 7.1, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:N/I:H/A:L", "classification": { "area": "authorization", "reason": "A skill name can escape the intended sandbox destination when files are mirrored.", "source": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "resolved_url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "api_url": "https://api.github.com/repos/openclaw/openclaw/security-advisories/GHSA-xw4p-pw82-hqr7", "state": "published", "ghsa_id": "GHSA-xw4p-pw82-hqr7", "cve_id": null, "summary": "Sandbox skill mirroring path traversal could write outside the sandbox workspace", "published_at": "2026-02-15T14:45:22Z", "updated_at": "2026-02-15T14:45:22Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-28457", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-28457", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-OPENCLAW-001/", "source_url": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-31801", "finding_id": "F-ZOT-AUTHZ-001", "repo": "project-zot/zot", "url": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "patched": "zot: v2.1.15", "status": "patched", "kind": "cve", "cvss": 7.7, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "resolved_url": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "api_url": "https://api.github.com/repos/project-zot/zot/security-advisories/GHSA-85jx-fm8m-x8c6", "state": "published", "ghsa_id": "GHSA-85jx-fm8m-x8c6", "cve_id": "CVE-2026-31801", "summary": "create-only policy allows overwrite attempts of existing latest tag (update permission not required)", "published_at": "2026-03-09T05:45:42Z", "updated_at": "2026-03-09T17:58:43Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-863" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "zot", "ecosystem": "go", "affected": "v1.3.0 through v2.1.14 (and `main` at commit `3c7d5a5f1d40eb996ba1d56f28be57a3b77510af`)", "patched": "v2.1.15" } ] }, "cve_publication": { "id": "CVE-2026-31801", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31801", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Create permission can be used to overwrite existing content.", "source": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ZOT-AUTHZ-001/", "source_url": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-31837", "finding_id": "F-ISTIO-JWKS-002", "repo": "istio/istio", "url": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "patched": "1.29.1, 1.28.5, 1.27.8", "status": "patched", "kind": "cve", "cvss": 8.7, "cvss_vector": null, "credit": "reported by 1seal (ISTIO-SECURITY-2026-001)", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "resolved_url": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "api_url": "https://api.github.com/repos/istio/istio/security-advisories/GHSA-v75c-crr9-733c", "state": "published", "ghsa_id": "GHSA-v75c-crr9-733c", "cve_id": "CVE-2026-31837", "summary": "JWKS Resolver Failure May Expose Hardcoded Default Keys", "published_at": "2026-03-10T17:50:53Z", "updated_at": "2026-03-10T17:50:53Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-31837", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31837", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "A hardcoded fallback key changes the signature-verification trust decision.", "source": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ISTIO-JWKS-002/", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "title": null, "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-31838", "finding_id": "F-ISTIO-XDSDEBUG-002", "repo": "istio/istio", "url": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "patched": "1.29.1, 1.28.5, 1.27.8", "status": "patched", "kind": "cve", "cvss": 6.9, "cvss_vector": null, "credit": "reported by 1seal (ISTIO-SECURITY-2026-001)", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "resolved_url": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "api_url": "https://api.github.com/repos/istio/istio/security-advisories/GHSA-974c-2wxh-g4ww", "state": "published", "ghsa_id": "GHSA-974c-2wxh-g4ww", "cve_id": "CVE-2026-31838", "summary": "Debug Endpoints Allow Cross-Namespace Proxy Data Access", "published_at": "2026-03-10T17:51:04Z", "updated_at": "2026-04-06T02:15:11Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-31838", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31838", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Debug access crosses namespace boundaries.", "source": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ISTIO-XDSDEBUG-002/", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-41413", "finding_id": "F-ISTIO-JWKS-001", "repo": "istio/istio", "url": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "patched": "1.29.2, 1.28.6", "status": "patched", "kind": "cve", "cvss": 5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N", "credit": "reporter: @1seal", "note": "GHSA-fgw5-hp8f-xfhc · SSRF via RequestAuthentication jwksUri", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "resolved_url": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "api_url": "https://api.github.com/repos/istio/istio/security-advisories/GHSA-fgw5-hp8f-xfhc", "state": "published", "ghsa_id": "GHSA-fgw5-hp8f-xfhc", "cve_id": "CVE-2026-41413", "summary": "SSRF via RequestAuthentication jwksUri", "published_at": "2026-04-15T21:20:03Z", "updated_at": "2026-04-20T16:20:34Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-41413", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-41413", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "JWKS fetching permits an untrusted outbound destination.", "source": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ISTIO-JWKS-001/", "source_url": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-28407", "finding_id": "F-MALCONTENT-010", "repo": "chainguard-dev/malcontent", "url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "patched": "malcontent v1.21.0", "status": "patched", "kind": "cve", "cvss": null, "cvss_vector": null, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "resolved_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "api_url": "https://api.github.com/repos/chainguard-dev/malcontent/security-advisories/GHSA-945p-3jhm-6rcp", "state": "published", "ghsa_id": "GHSA-945p-3jhm-6rcp", "cve_id": "CVE-2026-28407", "summary": "Nested archive extraction failure can drop content from scan inputs", "published_at": "2026-02-27T13:31:48Z", "updated_at": "2026-02-27T19:20:50Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-703" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-28407", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-28407", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "Failed nested archive extraction can omit content from scan inputs, so the integrity of the reported scan coverage is not preserved.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-010/", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-33211", "finding_id": "F-TEKTON-001-001", "repo": "tektoncd/pipeline", "url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "patched": "v1.0.1, v1.3.3, v1.6.1, v1.9.2, v1.10.2", "status": "patched", "kind": "cve", "cvss": 9.6, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "resolved_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "api_url": "https://api.github.com/repos/tektoncd/pipeline/security-advisories/GHSA-j5q5-j9gm-2w5c", "state": "published", "ghsa_id": "GHSA-j5q5-j9gm-2w5c", "cve_id": "CVE-2026-33211", "summary": "Path traversal in Tekton Pipelines git resolver allows reading arbitrary files from the resolver pod", "published_at": "2026-03-18T09:11:27Z", "updated_at": "2026-03-18T17:22:44Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-33211", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33211", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Git resolver traversal reaches files beyond the tenant's intended root.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TEKTON-001-001/", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-3547", "title": "wolfSSL: out-of-bounds read (DoS) in ALPN parsing due to incomplete validation", "finding_id": "F-WOLFSSL-ALPN-001", "repo": "wolfSSL/wolfssl", "url": "https://github.com/advisories/GHSA-f377-557w-vjgv", "patched": "wolfSSL 5.9.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "credit": "thanks to Oleh Konko (1seal) for the report (wolfSSL v5.9.0-stable release note)", "cve_publication": { "id": "CVE-2026-3547", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-3547", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "The published advisory describes an out-of-bounds read in ALPN list parsing.", "source": "https://github.com/advisories/GHSA-f377-557w-vjgv", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-ALPN-001/", "source_url": "https://github.com/advisories/GHSA-f377-557w-vjgv", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-3549", "title": "ECH parsing heap buffer overflow", "finding_id": "F-WOLFSSL-ECH-001", "repo": "wolfSSL/wolfssl", "url": "https://github.com/advisories/GHSA-j2g5-52p7-mfpc", "patched": "wolfSSL 5.9.0", "status": "patched", "kind": "cve", "cvss": 8.3, "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "credit": "thanks to Oleh Konko (1seal) for testing (wolfSSL v5.9.0-stable release note)", "cve_publication": { "id": "CVE-2026-3549", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-3549", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "An ECH length underflow produces a heap out-of-bounds write.", "source": "https://github.com/advisories/GHSA-j2g5-52p7-mfpc", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-ECH-001/", "source_url": "https://github.com/advisories/GHSA-j2g5-52p7-mfpc", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-5263", "title": "URI nameConstraints not enforced in ConfirmNameConstraints()", "finding_id": "F-WOLFSSL-NC-URI-001", "repo": "wolfSSL/wolfssl", "url": "https://github.com/advisories/GHSA-9xmr-c663-3rpr", "patched": "wolfSSL 5.9.1", "status": "patched", "kind": "cve", "cvss": 7, "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N", "credit": "finder: Oleh Konko @1seal (wolfSSL CNA / v5.9.1-stable release note)", "note": "GHSA-9xmr-c663-3rpr · fixed in PR 10048", "cve_publication": { "id": "CVE-2026-5263", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-5263", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "URI name-constraint parsing fails to enforce the intended certificate boundary.", "source": "https://github.com/advisories/GHSA-9xmr-c663-3rpr", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-NC-URI-001/", "source_url": "https://github.com/advisories/GHSA-9xmr-c663-3rpr", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-33022", "finding_id": "F-TEKTON-PANIC-001", "repo": "tektoncd/pipeline", "url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "patched": "github.com/tektoncd/pipeline: 1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2", "status": "patched", "kind": "cve", "cvss": 6.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "credit": "reporter: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "resolved_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "api_url": "https://api.github.com/repos/tektoncd/pipeline/security-advisories/GHSA-cv4x-93xx-wgfj", "state": "published", "ghsa_id": "GHSA-cv4x-93xx-wgfj", "cve_id": "CVE-2026-33022", "summary": "Tekton Pipelines controller panic via long resolver name in TaskRun/PipelineRun", "published_at": "2026-03-16T12:24:03Z", "updated_at": "2026-03-24T10:57:40Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-129" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "github.com/tektoncd/pipeline", "ecosystem": "go", "affected": ">= 0.60.0, <= 1.10.1", "patched": "1.0.1, 1.3.3, 1.6.1, 1.9.2, 1.10.2" } ] }, "cve_publication": { "id": "CVE-2026-33022", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33022", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "An oversized resolver name triggers a panic.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TEKTON-PANIC-001/", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-25542", "finding_id": "F-TEKTON-REGEX-001", "repo": "tektoncd/pipeline", "url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "patched": "github.com/tektoncd/pipeline: 1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1", "status": "patched", "kind": "cve", "cvss": 6.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N", "credit": "reporter: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "resolved_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "api_url": "https://api.github.com/repos/tektoncd/pipeline/security-advisories/GHSA-rmx9-2pp3-xhcr", "state": "published", "ghsa_id": "GHSA-rmx9-2pp3-xhcr", "cve_id": "CVE-2026-25542", "summary": "VerificationPolicy regex pattern bypass via substring matching", "published_at": "2026-04-21T14:13:11Z", "updated_at": "2026-04-21T14:13:11Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-185" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "github.com/tektoncd/pipeline", "ecosystem": "go", "affected": ">= 0.43.0, <= 1.7.0 (also present on main at 0133513db03dadb3cb08801d6b0330badcb63830)", "patched": "1.0.2, 1.3.4, 1.6.2, 1.9.3, 1.11.1" } ] }, "cve_publication": { "id": "CVE-2026-25542", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-25542", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A partial regular-expression match weakens the verification policy.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TEKTON-REGEX-001/", "source_url": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "GHSA-54p8-x2m9-c593", "finding_id": "F-MALCONTENT-006", "repo": "chainguard-dev/malcontent", "url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "patched": "malcontent v1.21.0", "status": "patched", "kind": "ghsa", "cve": null, "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "primary mapping; advisory text matches the late-defer/resource-leak fix train", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "resolved_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "api_url": "https://api.github.com/repos/chainguard-dev/malcontent/security-advisories/GHSA-54p8-x2m9-c593", "state": "published", "ghsa_id": "GHSA-54p8-x2m9-c593", "cve_id": null, "summary": "Error-path cleanup gap can leak scanners and fds and degrade availability", "published_at": "2026-02-27T13:43:12Z", "updated_at": "2026-02-27T15:58:16Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-400" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "classification": { "area": "availability", "reason": "Scanner resources and file descriptors are not reliably released.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-006/", "source_url": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-28402", "finding_id": "F-NIMIQ-TENDERMINT-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "patched": "nimiq-blockchain v1.2.2", "status": "patched", "kind": "cve", "cvss": 7.1, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-7wh6-rmxx-ww47", "state": "published", "ghsa_id": "GHSA-7wh6-rmxx-ww47", "cve_id": "CVE-2026-28402", "summary": "Missing proposal body root verification", "published_at": "2026-02-27T16:11:11Z", "updated_at": "2026-02-27T16:31:43Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-354" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-28402", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-28402", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "Proposal validation omits a required root check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-TENDERMINT-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-34061", "finding_id": "F-NIMIQ-INTERLINK-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "patched": "nimiq-blockchain v1.3.0", "status": "patched", "kind": "cve", "cvss": 4.9, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-gr83-j5f8-p2r5; patched in v1.3.0 via PR #3668", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-gr83-j5f8-p2r5", "state": "published", "ghsa_id": "GHSA-gr83-j5f8-p2r5", "cve_id": "CVE-2026-34061", "summary": "Macro block proposal interlink bug", "published_at": "2026-04-02T21:57:22Z", "updated_at": "2026-04-02T22:08:53Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-345" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34061", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34061", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "Macro block proposal verification omits the interlink commitment check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-INTERLINK-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-34068", "finding_id": "F-NIMIQ-ROGUEKEY-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 6.8, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N", "note": "GHSA-pf4j-pf3w-95f9; patched in v1.3.0 via PR #3654", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-pf4j-pf3w-95f9", "state": "published", "ghsa_id": "GHSA-pf4j-pf3w-95f9", "cve_id": "CVE-2026-34068", "summary": "`UpdateValidator` transactions allows voting key change without proof-of-knowledge", "published_at": "2026-04-22T01:01:48Z", "updated_at": "2026-04-22T01:01:48Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-347" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34068", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34068", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "A voting key is accepted without proof of knowledge, undermining the integrity of aggregate-signature verification.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-ROGUEKEY-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-34067", "finding_id": "F-NIMIQ-HISTORYPROOF-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 3.1, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-264v-m8fm-76jm", "state": "published", "ghsa_id": "GHSA-264v-m8fm-76jm", "cve_id": "CVE-2026-34067", "summary": "Panic via `HistoryTreeProof` length mismatch", "published_at": "2026-04-22T01:04:08Z", "updated_at": "2026-04-22T01:04:08Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-20", "CWE-617" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34067", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34067", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Malformed history proof input triggers a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-HISTORYPROOF-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34066", "finding_id": "F-NIMIQ-HISTORYSYNC-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:H", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-j99g-7rqw-q9jg", "state": "published", "ghsa_id": "GHSA-j99g-7rqw-q9jg", "cve_id": "CVE-2026-34066", "summary": "Peer-triggerable panic during history sync", "published_at": "2026-04-22T01:07:37Z", "updated_at": "2026-04-22T01:07:37Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-20", "CWE-617", "CWE-754" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34066", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34066", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "History synchronization input violates parser state assumptions.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-HISTORYSYNC-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34065", "finding_id": "F-NIMIQ-VALIDATORSKEY-PANIC-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-7c4j-2m43-2mgh", "state": "published", "ghsa_id": "GHSA-7c4j-2m43-2mgh", "cve_id": "CVE-2026-34065", "summary": "Peer-triggerable crash via invalid election macro validators voting key hashing announced macro blocks", "published_at": "2026-04-22T01:11:23Z", "updated_at": "2026-04-22T01:11:23Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-20", "CWE-252", "CWE-755" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34065", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34065", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Malformed validator-key input triggers a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-VALIDATORSKEY-PANIC-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34064", "finding_id": "F-NIMIQ-VESTING-MINCAP-UNDERFLOW-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-vc34-39q2-m6q3", "state": "published", "ghsa_id": "GHSA-vc34-39q2-m6q3", "cve_id": "CVE-2026-34064", "summary": "Vesting insufficient funds error can panic", "published_at": "2026-04-22T01:16:47Z", "updated_at": "2026-04-22T01:16:47Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-191" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34064", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34064", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Vesting arithmetic underflow triggers a panic; memory corruption is not asserted.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-VESTING-MINCAP-UNDERFLOW-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-33471", "finding_id": "F-NIMIQ-SKIPBLOCK-QUORUMBYPASS-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 9.6, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-6973-8887-87ff", "state": "published", "ghsa_id": "GHSA-6973-8887-87ff", "cve_id": "CVE-2026-33471", "summary": "skip block quorum bypass via out-of-range BitSet indices + u16 truncation", "published_at": "2026-04-22T01:19:58Z", "updated_at": "2026-04-22T01:19:58Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-20", "CWE-190", "CWE-345", "CWE-1284" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-33471", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33471", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "integrity", "reason": "A truncated signer bitset bypasses a quorum check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-SKIPBLOCK-QUORUMBYPASS-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-28406", "finding_id": "F-CHAINGUARD-FORKS-KANIKO-AG5-001", "repo": "chainguard-forks/kaniko", "url": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "patched": null, "status": "unpatched", "kind": "cve", "cvss": 8.2, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L", "classification": { "area": "authorization", "reason": "Build-context archive paths can escape the extraction directory; the primary defect is missing path containment.", "source": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "resolved_url": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "api_url": "https://api.github.com/repos/chainguard-forks/kaniko/security-advisories/GHSA-6rxq-q92g-4rmf", "state": "published", "ghsa_id": "GHSA-6rxq-q92g-4rmf", "cve_id": "CVE-2026-28406", "summary": "tar archive path traversal in build context extraction allows writing files outside destination directory", "published_at": "2026-02-27T19:03:39Z", "updated_at": "2026-02-27T19:19:27Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "", "ecosystem": "go", "affected": ">= 1.25.4, <= 1.25.7", "patched": "" } ] }, "cve_publication": { "id": "CVE-2026-28406", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-28406", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-CHAINGUARD-FORKS-KANIKO-AG5-001/", "source_url": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-29049", "finding_id": "F-MELANGE-003", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "patched": "package name not specified: v0.43.4", "status": "patched", "kind": "cve", "cvss": 4.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-7rp8-r62p-q6wc", "state": "published", "ghsa_id": "GHSA-7rp8-r62p-q6wc", "cve_id": "CVE-2026-29049", "summary": "unbounded HTTP download in `melange update-cache` can exhaust disk in CI", "published_at": "2026-03-02T14:32:04Z", "updated_at": "2026-06-15T14:43:18Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-400", "CWE-918" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "", "ecosystem": "go", "affected": "\\<= 0.40.5", "patched": "v0.43.4" } ] }, "cve_publication": { "id": "CVE-2026-29049", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29049", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Downloads can exhaust disk space without an effective limit.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-003/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-29050", "finding_id": "F-MELANGE-008", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "patched": "melange v0.43.4", "status": "patched", "kind": "cve", "note": "GHSA-98f2-w9h9-7fp9 · external pipeline resolver path traversal", "credit": "reporter: @1seal", "cvss": 6.1, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-98f2-w9h9-7fp9", "state": "published", "ghsa_id": "GHSA-98f2-w9h9-7fp9", "cve_id": "CVE-2026-29050", "summary": "Path traversal in melange's external pipeline resolver (pipeline[].uses) allows loading a pipeline from outside the pipeline directories", "published_at": "2026-04-23T21:06:26Z", "updated_at": "2026-04-23T21:06:26Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-29050", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29050", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "External pipeline resolution escapes the intended directory.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-008/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-29051", "finding_id": "F-MELANGE-004", "repo": "chainguard-dev/melange", "url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "patched": "melange v0.43.4", "status": "patched", "kind": "cve", "note": "GHSA-q2pw-xx38-p64j · --persist-lint-results path traversal", "credit": "reporter: @1seal", "cvss": 4.4, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "resolved_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "api_url": "https://api.github.com/repos/chainguard-dev/melange/security-advisories/GHSA-q2pw-xx38-p64j", "state": "published", "ghsa_id": "GHSA-q2pw-xx38-p64j", "cve_id": "CVE-2026-29051", "summary": "Path traversal in melange --persist-lint-results via unvalidated .PKGINFO fields", "published_at": "2026-04-23T21:06:27Z", "updated_at": "2026-04-23T21:06:27Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-22" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-29051", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29051", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Package metadata influences an unchecked filesystem path.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MELANGE-004/", "source_url": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-21518", "finding_id": "F-VSCODE-MCP-001", "repo": "microsoft/vscode", "url": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "patched": "VS Code 1.109.1", "status": "patched", "kind": "cve", "note": "GHSA-6xq8-9qf3-p6qv · metadata correction requested", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:N", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "resolved_url": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "api_url": "https://api.github.com/repos/microsoft/vscode/security-advisories/GHSA-6xq8-9qf3-p6qv", "state": "published", "ghsa_id": "GHSA-6xq8-9qf3-p6qv", "cve_id": "CVE-2026-21518", "summary": "Workspace trust for MCP servers", "published_at": "2026-02-10T18:18:23Z", "updated_at": "2026-02-10T18:18:23Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "cve_publication": { "id": "CVE-2026-21518", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-21518", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "The recorded report concerns bypassing the MCP workspace trust boundary.", "source": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-VSCODE-MCP-001/", "source_url": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-21523", "title": "GitHub Copilot and Visual Studio Code Remote Code Execution Vulnerability", "finding_id": "F-VSCODE-COPILOT-001", "repo": "microsoft/vscode", "url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21523", "patched": "VS Code 1.110.1; VS Code Copilot Chat Extension 0.37.1", "status": "patched", "kind": "cve", "cvss": 8, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "note": "MSRC: GitHub Copilot and Visual Studio Code Remote Code Execution Vulnerability. MSRC revision history added acknowledgements on 2026-04-20 as an informational change; official acknowledgement lists Oleh Konko with 1seal. caveat: the public MCP-specific advisory GHSA-6xq8-9qf3-p6qv maps to CVE-2026-21518, so exact local finding-to-CVE mapping for F-VSCODE-MCP-001 vs CVE-2026-21523 depends on the private MSRC thread.", "credit": "MSRC acknowledgement: Oleh Konko with 1seal", "cve_publication": { "id": "CVE-2026-21523", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-21523", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "unclassified", "reason": "Public CVE credit is recorded, but its multiple advisory variants do not establish this finding's exact mechanism.", "source": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21523", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-VSCODE-COPILOT-001/", "source_url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21523", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "id": "CVE-2026-3842", "title": "Qemu-kvm: hyperv/syndbg: missing mapped-length guard after cpu_physical_memory_map causes host oob write", "finding_id": "F-QEMU-001-001", "repo": "qemu/qemu", "url": "https://access.redhat.com/security/cve/cve-2026-3842", "patched": "upstream commit 4f28b87fdd24", "status": "patched", "kind": "cve", "credit": "Reported-by: Oleh Konko ", "note": "public Red Hat CVE record; upstream QEMU commit 4f28b87fdd24df2049626106b7c24d0180952115 from 2026-03-09 carries Fixes: CVE-2026-3842 and Reported-by: Oleh Konko; public backport/cherry-pick 85af4e93 followed on 2026-03-13.", "cve_publication": { "id": "CVE-2026-3842", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-3842", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "Mapped physical-memory length is not checked before the affected access.", "source": "https://github.com/qemu/qemu/commit/4f28b87fdd24df2049626106b7c24d0180952115", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-QEMU-001-001/", "source_url": "https://access.redhat.com/security/cve/cve-2026-3842", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-34040", "finding_id": "F-MOBY-001-001", "repo": "moby/moby", "url": "https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2", "patched": "Docker Engine: 29.3.1", "status": "patched", "kind": "cve", "cvss": 8.8, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H", "note": "GHSA-x744-4wpc-v9h2", "credit": "1seal / Oleh Konko (@1seal)", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2", "resolved_url": "https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2", "api_url": "https://api.github.com/repos/moby/moby/security-advisories/GHSA-x744-4wpc-v9h2", "state": "published", "ghsa_id": "GHSA-x744-4wpc-v9h2", "cve_id": "CVE-2026-34040", "summary": "AuthZ plugin bypass with oversized request body", "published_at": "2026-03-25T17:46:34Z", "updated_at": "2026-03-27T00:04:55Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "Docker Engine", "ecosystem": "", "affected": "< 29.3.1", "patched": "29.3.1" } ] }, "cve_publication": { "id": "CVE-2026-34040", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34040", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "An oversized request body bypasses the authorization plugin decision.", "source": "https://github.com/moby/moby/commit/7a767b27fd1238c89a5cc926c39e27d3bcf58e35", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-MOBY-001-001/", "source_url": "https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-33540", "finding_id": "F-DIST-PROXY-SSRF-001", "repo": "distribution/distribution", "url": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "patched": "distribution: >=3.1.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "note": "GHSA-3p65-76g6-3w7r", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "resolved_url": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "api_url": "https://api.github.com/repos/distribution/distribution/security-advisories/GHSA-3p65-76g6-3w7r", "state": "published", "ghsa_id": "GHSA-3p65-76g6-3w7r", "cve_id": "CVE-2026-33540", "summary": "Pull-through cache credential exfiltration via www-authenticate bearer realm", "published_at": "2026-04-06T13:59:09Z", "updated_at": "2026-04-06T18:33:04Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-918" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "distribution", "ecosystem": "go", "affected": "<= 3.0.0", "patched": ">=3.1.0" } ] }, "cve_publication": { "id": "CVE-2026-33540", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33540", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A registry-controlled realm redirects credential-bearing token requests.", "source": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-DIST-PROXY-SSRF-001/", "source_url": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-35172", "finding_id": "F-DIST-REDIS-REVIVAL-001", "repo": "distribution/distribution", "url": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "patched": "package name not specified: >=3.1.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "note": "GHSA-f2g3-hh2r-cwgc", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "resolved_url": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "api_url": "https://api.github.com/repos/distribution/distribution/security-advisories/GHSA-f2g3-hh2r-cwgc", "state": "published", "ghsa_id": "GHSA-f2g3-hh2r-cwgc", "cve_id": "CVE-2026-35172", "summary": "Stale blob access resurrection via repo-scoped redis descriptor cache invalidation", "published_at": "2026-04-06T13:59:30Z", "updated_at": "2026-04-06T18:32:41Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-284" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "", "ecosystem": "go", "affected": "<= 3.0.x, <= 2.8.x when redis blob descriptor cache and delete are both enabled", "patched": ">=3.1.0" } ] }, "cve_publication": { "id": "CVE-2026-35172", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-35172", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Stale cached access state revives access that should no longer be granted.", "source": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-DIST-REDIS-REVIVAL-001/", "source_url": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-29181", "finding_id": "F-OTELGO-001", "repo": "open-telemetry/opentelemetry-go", "url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "patched": "go.opentelemetry.io/otel/baggage: v1.41.0; go.opentelemetry.io/otel/propagation: v1.41.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-mh2q-q3fh-2475", "classification": { "area": "availability", "reason": "Repeated baggage header values amplify parsing work and allocations beyond the per-value limit.", "source": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "resolved_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "api_url": "https://api.github.com/repos/open-telemetry/opentelemetry-go/security-advisories/GHSA-mh2q-q3fh-2475", "state": "published", "ghsa_id": "GHSA-mh2q-q3fh-2475", "cve_id": "CVE-2026-29181", "summary": "multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)", "published_at": "2026-04-07T18:34:27Z", "updated_at": "2026-04-07T18:34:27Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-400" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "go.opentelemetry.io/otel/baggage", "ecosystem": "go", "affected": ">= v1.36.0, <= 1.40.0", "patched": "v1.41.0" }, { "name": "go.opentelemetry.io/otel/propagation", "ecosystem": "go", "affected": ">= v1.36.0, <= 1.40.0", "patched": "v1.41.0" } ] }, "cve_publication": { "id": "CVE-2026-29181", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-29181", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-OTELGO-001/", "source_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-39882", "finding_id": "F-OTELGO-002", "repo": "open-telemetry/opentelemetry-go", "url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "patched": "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp: v1.43.0; go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp: v1.43.0; go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp: v0.19.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-w8rr-5gcm-pp58", "classification": { "area": "availability", "reason": "An untrusted collector response can trigger unbounded buffering and exhaust exporter memory.", "source": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "resolved_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "api_url": "https://api.github.com/repos/open-telemetry/opentelemetry-go/security-advisories/GHSA-w8rr-5gcm-pp58", "state": "published", "ghsa_id": "GHSA-w8rr-5gcm-pp58", "cve_id": "CVE-2026-39882", "summary": "OTLP HTTP exporters read unbounded HTTP response bodies", "published_at": "2026-04-08T14:39:01Z", "updated_at": "2026-04-08T14:39:01Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-789" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp", "ecosystem": "go", "affected": "< v1.43.0", "patched": "v1.43.0" }, { "name": "go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp", "ecosystem": "go", "affected": "< v1.43.0", "patched": "v1.43.0" }, { "name": "go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp", "ecosystem": "go", "affected": "< v0.19.0", "patched": "v0.19.0" } ] }, "cve_publication": { "id": "CVE-2026-39882", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-39882", "fetched_at": "2026-09-23T20:30:40.966Z" }, "cvss_assessment": { "version": "3.1", "score": 5.3, "vector": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "assessor": "OpenTelemetry (repository advisory)", "source_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "observed_at": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-OTELGO-002/", "source_url": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-40182", "finding_id": "F-OTELGO-002", "repo": "open-telemetry/opentelemetry-dotnet", "url": "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933", "patched": "1.15.2", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-q834-8qmm-v933 · surfaced during investigation of GHSA-w8rr-5gcm-pp58", "credit": "reporter: @1seal", "classification": { "area": "availability", "reason": "OTLP error responses are buffered without a size limit, allowing a malicious collector to exhaust application memory.", "source": "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933", "resolved_url": "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933", "api_url": "https://api.github.com/repos/open-telemetry/opentelemetry-dotnet/security-advisories/GHSA-q834-8qmm-v933", "state": "published", "ghsa_id": "GHSA-q834-8qmm-v933", "cve_id": "CVE-2026-40182", "summary": "OTLP exporter reads unbounded HTTP response bodies", "published_at": "2026-04-23T15:36:14Z", "updated_at": "2026-04-23T15:36:14Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-789" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-40182", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-40182", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-OTELGO-002/", "source_url": "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-33810", "title": "Case-sensitive excludedSubtrees name constraints cause Auth Bypass in crypto/x509", "finding_id": "F-GO-X509-WILDCARD-CASE-001", "repo": "golang/go", "url": "https://github.com/advisories/GHSA-fv83-x2xw-2j55", "patched": "go1.26.2", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "note": "GHSA-fv83-x2xw-2j55", "credit": "public credit to @1seal in golang/go#78332", "classification": { "area": "identity", "reason": "Excluded certificate DNS constraints fail to cover differently cased wildcard names, weakening certificate identity validation.", "source": "https://github.com/advisories/GHSA-fv83-x2xw-2j55", "reviewed": "2026-09-21" }, "cve_publication": { "id": "CVE-2026-33810", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-33810", "fetched_at": "2026-09-23T20:30:40.966Z" }, "cvss_assessment": { "version": "3.1", "score": 7.5, "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N", "assessor": "CISA ADP", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-33810", "observed_at": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-GO-X509-WILDCARD-CASE-001/", "source_url": "https://github.com/advisories/GHSA-fv83-x2xw-2j55", "disclosed": null, "cwe": null, "layer": "identity" }, { "id": "CVE-2026-35206", "finding_id": "F-HELM-UNTAR-ROOT-COLLAPSE-001", "repo": "helm/helm", "url": "https://github.com/helm/helm/security/advisories/GHSA-hr2v-4r36-88hr", "patched": "3.20.2, 4.1.4", "status": "patched", "kind": "cve", "cvss": 4.8, "cvss_vector": "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N", "note": "GHSA-hr2v-4r36-88hr", "credit": "Oleh Konko (@1seal)", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/helm/helm/security/advisories/GHSA-hr2v-4r36-88hr", "resolved_url": "https://github.com/helm/helm/security/advisories/GHSA-hr2v-4r36-88hr", "api_url": "https://api.github.com/repos/helm/helm/security-advisories/GHSA-hr2v-4r36-88hr", "state": "published", "ghsa_id": "GHSA-hr2v-4r36-88hr", "cve_id": "CVE-2026-35206", "summary": "Helm Chart extraction output directory collapse via `Chart.yaml` name dot-segment", "published_at": "2026-04-09T20:22:55Z", "updated_at": "2026-04-09T20:22:55Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-35206", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-35206", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Archive root handling defeats extraction containment.", "source": "https://github.com/helm/helm/releases/tag/v4.1.4", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-HELM-UNTAR-ROOT-COLLAPSE-001/", "source_url": "https://github.com/helm/helm/security/advisories/GHSA-hr2v-4r36-88hr", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-40097", "finding_id": "F-SMALLSTEP-AK-EKU-001", "repo": "smallstep/certificates", "url": "https://github.com/smallstep/certificates/security/advisories/GHSA-9qq8-cgcv-qmc9", "patched": "v0.30.0", "status": "patched", "kind": "cve", "cvss": 3.7, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "GHSA-9qq8-cgcv-qmc9", "credit": "Oleh Konko (@1seal)", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/smallstep/certificates/security/advisories/GHSA-9qq8-cgcv-qmc9", "resolved_url": "https://github.com/smallstep/certificates/security/advisories/GHSA-9qq8-cgcv-qmc9", "api_url": "https://api.github.com/repos/smallstep/certificates/security-advisories/GHSA-9qq8-cgcv-qmc9", "state": "published", "ghsa_id": "GHSA-9qq8-cgcv-qmc9", "cve_id": "CVE-2026-40097", "summary": "Index out-of-bounds panic via crafted AK certificate with empty EKU in TPM device attestation", "published_at": "2026-04-10T01:57:13Z", "updated_at": "2026-04-10T01:57:13Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-129" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-40097", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-40097", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "An empty EKU input reaches a panic, not an established authorization bypass.", "source": "https://github.com/smallstep/certificates/pull/2569", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-SMALLSTEP-AK-EKU-001/", "source_url": "https://github.com/smallstep/certificates/security/advisories/GHSA-9qq8-cgcv-qmc9", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-32605", "finding_id": "F-NIMIQ-PROPOSAL-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA-g99c-h7j7-rfhv", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-g99c-h7j7-rfhv", "state": "published", "ghsa_id": "GHSA-g99c-h7j7-rfhv", "cve_id": "CVE-2026-32605", "summary": "Remote crash via off-by-one signer bounds check in proposal buffer", "published_at": "2026-04-11T01:54:19Z", "updated_at": "2026-04-11T01:54:19Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-125", "CWE-193" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-32605", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-32605", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "A signer-index boundary error triggers a checked-language panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-PROPOSAL-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-34069", "finding_id": "F-NIMIQ-MACROCHAIN-001", "repo": "nimiq/core-rs-albatross", "url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "patched": "v1.3.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "note": "GHSA-48m6-486p-9j8p; patched in v1.3.0 via PR #3660", "credit": "finder: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "resolved_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "api_url": "https://api.github.com/repos/nimiq/core-rs-albatross/security-advisories/GHSA-48m6-486p-9j8p", "state": "published", "ghsa_id": "GHSA-48m6-486p-9j8p", "cve_id": "CVE-2026-34069", "summary": "Panic via RequestMacroChain micro-block locator", "published_at": "2026-04-11T02:05:04Z", "updated_at": "2026-04-11T02:05:04Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-617" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-34069", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-34069", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Macro-chain input reaches an invalid state and panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-MACROCHAIN-001/", "source_url": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-40868", "finding_id": "F-KYVERNO-APICALL-001", "repo": "kyverno/kyverno", "url": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "patched": "1.16.4", "status": "patched", "kind": "cve", "cvss": 8.1, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N", "credit": "reporter: @1seal", "note": "GHSA-q93q-v844-jrqp", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "resolved_url": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "api_url": "https://api.github.com/repos/kyverno/kyverno/security-advisories/GHSA-q93q-v844-jrqp", "state": "published", "ghsa_id": "GHSA-q93q-v844-jrqp", "cve_id": "CVE-2026-40868", "summary": "kyverno apicall servicecall implicit bearer token injection leaks kyverno serviceaccount token", "published_at": "2026-04-13T04:55:18Z", "updated_at": "2026-06-30T20:18:53Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-40868", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-40868", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A policy-controlled API destination receives ambient credentials.", "source": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-KYVERNO-APICALL-001/", "source_url": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-54334", "finding_id": "F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003", "repo": "theopolis/uefi-firmware-parser", "url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-hm2w-vr2p-hq7w", "patched": "CVE record: 1.14; GHSA: 1.13 (conflicting version metadata)", "status": "patched", "kind": "cve", "cve": "CVE-2026-54334", "cvss": 9.8, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "credit": "reporter: @1seal", "note": "PR #145 · fix commit bf3dfaa8a05675bae6ea0cbfa082ddcebfcde23e. CVE-2026-54334: GitHub_M CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-14. The CNA record and repository GHSA disagree on the patched version; neither is silently substituted for the other.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-hm2w-vr2p-hq7w", "resolved_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-hm2w-vr2p-hq7w", "api_url": "https://api.github.com/repos/theopolis/uefi-firmware-parser/security-advisories/GHSA-hm2w-vr2p-hq7w", "state": "published", "ghsa_id": "GHSA-hm2w-vr2p-hq7w", "cve_id": "CVE-2026-54334", "summary": "Heap out-of-bounds write in tiano decompressor `ReadCLen`", "published_at": "2026-04-14T19:08:57Z", "updated_at": "2026-06-15T15:33:12Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "ghsa": "GHSA-hm2w-vr2p-hq7w", "cve_publication": { "id": "CVE-2026-54334", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-54334", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "Tiano ReadCLen writes outside the intended buffer.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003/", "source_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-hm2w-vr2p-hq7w", "title": null, "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-54333", "finding_id": "F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002", "repo": "theopolis/uefi-firmware-parser", "url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-2689-5p89-6j3j", "patched": "CVE record: 1.14; GHSA: 1.13 (conflicting version metadata)", "status": "patched", "kind": "cve", "cve": "CVE-2026-54333", "cvss": 9.8, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "credit": "reporter: @1seal", "note": "PR #145 · fix commit bf3dfaa8a05675bae6ea0cbfa082ddcebfcde23e. CVE-2026-54333: GitHub_M CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-14. The CNA record and repository GHSA disagree on the patched version; neither is silently substituted for the other.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-2689-5p89-6j3j", "resolved_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-2689-5p89-6j3j", "api_url": "https://api.github.com/repos/theopolis/uefi-firmware-parser/security-advisories/GHSA-2689-5p89-6j3j", "state": "published", "ghsa_id": "GHSA-2689-5p89-6j3j", "cve_id": "CVE-2026-54333", "summary": "Stack out-of-bounds write in tiano decompressor MakeTable", "published_at": "2026-04-14T19:09:14Z", "updated_at": "2026-06-15T15:33:01Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-787" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "ghsa": "GHSA-2689-5p89-6j3j", "cve_publication": { "id": "CVE-2026-54333", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-54333", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "Tiano MakeTable writes outside the intended buffer.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002/", "source_url": "https://github.com/theopolis/uefi-firmware-parser/security/advisories/GHSA-2689-5p89-6j3j", "title": null, "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "GHSA-pmwq-pjrm-6p5r", "finding_id": "F-INTOTO-CROSS-IMPL-001", "repo": "in-toto/in-toto-golang", "url": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "patched": "in-toto-golang v0.11.0", "status": "patched", "kind": "ghsa", "cve": null, "cvss": 4.1, "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N", "credit": "finder: @1seal", "note": "public advisory GHSA-pmwq-pjrm-6p5r covers the cross-implementation negation mismatch; affected <0.11.0, patched in 0.11.0 via in-toto-golang PR #462 / commit 36d782f. the earlier GHSA-28fv-f52p-hvwh reference is not publicly accessible.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "resolved_url": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "api_url": "https://api.github.com/repos/in-toto/in-toto-golang/security-advisories/GHSA-pmwq-pjrm-6p5r", "state": "published", "ghsa_id": "GHSA-pmwq-pjrm-6p5r", "cve_id": null, "summary": "Inconsistent negation behavior between in-toto-golang and in-toto-python", "published_at": "2026-05-05T19:56:38Z", "updated_at": "2026-05-05T19:56:38Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "classification": { "area": "semantics", "reason": "The same negated artifact rule has different meanings in Go and Python, so declared policy and executed policy can diverge.", "source": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "reviewed": "2026-09-24" }, "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-INTOTO-CROSS-IMPL-001/", "source_url": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "title": null, "disclosed": null, "cwe": null, "layer": "semantics" }, { "id": "CVE-2026-4525", "title": "Vault Token Leaked to Backends via Authorization: Bearer Passthrough Header", "finding_id": "F-VAULT-AUTHZ-BEARER-TOKEN-LEAK-001", "repo": "hashicorp/vault", "url": "https://discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344", "patched": "2.0.0, 1.21.5, 1.20.10, 1.19.16", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H", "credit": "identified and reported by Oleh Konko of 1seal (HCSEC-2026-07)", "note": "Vault token leaked to auth plugin backends via Authorization: Bearer passthrough header", "cve_publication": { "id": "CVE-2026-4525", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-4525", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "confidentiality", "reason": "An authorization bearer token is exposed through backend header forwarding.", "source": "https://discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-VAULT-AUTHZ-BEARER-TOKEN-LEAK-001/", "source_url": "https://discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "id": "CVE-2026-5052", "title": "Vault Vulnerable to Server-Side Request Forgery in ACME Challenge Validation via Attacker-Controlled DNS", "finding_id": "F-VAULT-ACME-SSRF-001", "repo": "hashicorp/vault", "url": "https://github.com/advisories/GHSA-8r5m-3f66-qpr3", "patched": "Vault CE 2.0.0; Vault Enterprise 2.0.0, 1.21.5, 1.20.10, 1.19.16", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "credit": "independently identified and reported by Oleh Konko of 1seal (HCSEC-2026-06)", "note": "GHSA-8r5m-3f66-qpr3 / HCSEC-2026-06; Vault ACME validation did not reject local targets for http-01 and tls-alpn-01 challenges. v2.0.0 adds isValidChallengeIP and dialACMEValidationTarget, plus challenge_permitted_ip_ranges and challenge_excluded_ip_ranges configuration.", "cve_publication": { "id": "CVE-2026-5052", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-5052", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "ACME validation dials attacker-controlled DNS destinations.", "source": "https://github.com/advisories/GHSA-8r5m-3f66-qpr3", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-VAULT-ACME-SSRF-001/", "source_url": "https://github.com/advisories/GHSA-8r5m-3f66-qpr3", "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-2092", "finding_id": "F-KEYCLOAK-SAML-001", "repo": "keycloak/keycloak", "url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "patched": "26.2.14, 26.4.10, 26.5.5, 26.6.0", "status": "patched", "kind": "cve", "cvss": 7.7, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L", "cwe": "CWE-1287", "note": "GHSA-794g-x443-36f7; improper validation of encrypted SAML assertions can allow unauthorized access via crafted SAML response.", "credit": "reporter: @1seal", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "resolved_url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "api_url": "https://api.github.com/repos/keycloak/keycloak/security-advisories/GHSA-794g-x443-36f7", "state": "published", "ghsa_id": "GHSA-794g-x443-36f7", "cve_id": "CVE-2026-2092", "summary": "Keycloak: Unauthorized access via improper validation of encrypted SAML assertions", "published_at": "2026-05-29T15:20:22Z", "updated_at": "2026-05-29T15:20:22Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-1287" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-2092", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-2092", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Insufficient validation of encrypted SAML assertions permits unauthorized authentication; the affected property is the asserted user identity.", "source": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-KEYCLOAK-SAML-001/", "source_url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "title": null, "disclosed": null, "layer": "identity" }, { "id": "CVE-2026-6550", "finding_id": "F-AWS-ENCRYPTION-SDK-PYTHON-001", "repo": "aws/aws-encryption-sdk-python", "url": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "patched": "3.3.1, 4.0.5", "status": "patched", "kind": "cve", "cvss": 4.7, "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N", "credit": "acknowledgement: 1seal.org", "note": "GHSA-v638-38fc-rhfv · AWS-2026-017", "classification": { "area": "integrity", "reason": "Shared cached encryption materials can bypass key commitment, undermining the binding between ciphertext and plaintext.", "source": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "resolved_url": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "api_url": "https://api.github.com/repos/aws/aws-encryption-sdk-python/security-advisories/GHSA-v638-38fc-rhfv", "state": "published", "ghsa_id": "GHSA-v638-38fc-rhfv", "cve_id": "CVE-2026-6550", "summary": "Key commitment policy bypass via shared key cache in AWS Encryption SDK for Python", "published_at": "2026-04-20T19:23:22Z", "updated_at": "2026-04-20T19:23:22Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "cve_publication": { "id": "CVE-2026-6550", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-6550", "fetched_at": "2026-09-23T20:30:40.966Z" }, "cvss_assessment": { "version": "3.1", "score": 4.7, "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N", "assessor": "AMZN CNA", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-6550", "observed_at": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-ENCRYPTION-SDK-PYTHON-001/", "source_url": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "title": null, "disclosed": null, "cwe": null, "layer": "integrity" }, { "id": "CVE-2026-5190", "finding_id": "F-AWS-EVENT-STREAM-001", "repo": "aws/aws-sdk-cpp", "url": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "patched": "aws-c-event-stream 0.6.0; aws-sdk-cpp 1.11.764", "status": "patched", "kind": "cve", "cvss": 7.7, "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N", "credit": "acknowledgement: Oleh Konko from 1seal / 1seal.org", "note": "GHSA-xvjw-fjq5-68hf / AWS-2026-011; AWS Common Runtime event-stream decoder memory corruption affecting aws-sdk-cpp <1.11.764 and other SDKs that expose event-stream functionality.", "classification": { "area": "memory-safety", "reason": "Crafted event-stream messages can corrupt decoder memory in a client application.", "source": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "resolved_url": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "api_url": "https://api.github.com/repos/awslabs/aws-c-event-stream/security-advisories/GHSA-xvjw-fjq5-68hf", "state": "published", "ghsa_id": "GHSA-xvjw-fjq5-68hf", "cve_id": "CVE-2026-5190", "summary": "Memory Corruption in event-stream parsing of headers", "published_at": "2026-03-31T17:11:08Z", "updated_at": "2026-03-31T17:12:58Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "cve_publication": { "id": "CVE-2026-5190", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-5190", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-EVENT-STREAM-001/", "source_url": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "title": null, "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-89090", "finding_id": "F-AWS-SDK-GO-V2-ES-001", "repo": "aws/aws-sdk-go-v2", "url": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "patched": "aws/protocol/eventstream v1.7.8; service-specific versions listed in the advisory", "status": "patched", "kind": "cve", "cve": "CVE-2026-89090", "credit": "reporter: @1seal (accepted); AWS acknowledgement: Oleh Konko (@1seal)", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "note": "GHSA published on 2026-04-07 for the unknown eventstream header value type panic fixed upstream in #3355. CVE-2026-89090: AMZN CNA record verified PUBLISHED on 2026-09-23; CVE publication 2026-09-11. Score shown is AWS CNA CVSS v3.1; the CNA also publishes a separate CVSS v4.0 assessment.", "classification": { "area": "availability", "reason": "An unknown EventStream header value type causes process termination in the Go decoder.", "source": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "resolved_url": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "api_url": "https://api.github.com/repos/aws/aws-sdk-go-v2/security-advisories/GHSA-xmrv-pmrh-hhx2", "state": "published", "ghsa_id": "GHSA-xmrv-pmrh-hhx2", "cve_id": "CVE-2026-89090", "summary": "Denial of Service due to Panic in AWS SDK for Go v2 SDK EventStream Decoder", "published_at": "2026-04-07T21:01:36Z", "updated_at": "2026-09-24T18:43:01Z", "withdrawn_at": null, "fetched_at": "2026-09-24T18:45:39Z", "cwes": [ "CWE-248" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "ghsa": "GHSA-xmrv-pmrh-hhx2", "cve_publication": { "id": "CVE-2026-89090", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-89090", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-SDK-GO-V2-ES-001/", "source_url": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "title": null, "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-6966", "finding_id": "F-AWS-TOUGH-001", "repo": "awslabs/tough", "url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "patched": "tough 0.22.0, tuftool 0.15.0", "status": "patched", "kind": "cve", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N", "credit": "reporter: @1seal; acknowledgement: Oleh Konko of 1seal", "note": "GHSA-8m7c-8m39-rv4x · signature threshold bypass in delegated roles", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "resolved_url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "api_url": "https://api.github.com/repos/awslabs/tough/security-advisories/GHSA-8m7c-8m39-rv4x", "state": "published", "ghsa_id": "GHSA-8m7c-8m39-rv4x", "cve_id": "CVE-2026-6966", "summary": "Signature Threshold Bypass in awslabs/tough Delegated Roles", "published_at": "2026-04-24T19:57:30Z", "updated_at": "2026-04-24T19:57:30Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-6966", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-6966", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Metadata signature thresholds are not correctly enforced.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-TOUGH-001/", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-6967", "finding_ids": [ "F-AWS-TOUGH-002", "F-AWS-TOUGH-003", "F-AWS-TOUGH-004", "F-AWS-TOUGH-005" ], "repo": "awslabs/tough", "url": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "patched": "tough 0.22.0, tuftool 0.15.0", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L", "credit": "reporter: @1seal; acknowledgement: Oleh Konko of 1seal", "note": "GHSA-4v58-8p28-2rq3 · missing expiration, hash, and length enforcement in delegated metadata validation; includes the local metadata cache poisoning variant tracked as F-AWS-TOUGH-005", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "resolved_url": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "api_url": "https://api.github.com/repos/awslabs/tough/security-advisories/GHSA-4v58-8p28-2rq3", "state": "published", "ghsa_id": "GHSA-4v58-8p28-2rq3", "cve_id": "CVE-2026-6967", "summary": "Missing Delegated Metadata Validation in awslabs/tough", "published_at": "2026-04-24T19:57:20Z", "updated_at": "2026-04-24T19:57:20Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-6967", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-6967", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Metadata validation fails to enforce the required trust checks. Unvalidated metadata can poison the trusted local cache.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-TOUGH-002/", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-6968", "finding_ids": [ "F-AWS-TOUGH-007", "F-AWS-TOUGH-008", "F-AWS-TOUGH-009" ], "repo": "awslabs/tough", "url": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "patched": "tough 0.22.0, tuftool 0.15.0", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L", "credit": "reporter: @1seal; acknowledgement: Oleh Konko of 1seal", "note": "GHSA-v57p-gppj-p9vg · multiple path traversal variants in tough write paths", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "resolved_url": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "api_url": "https://api.github.com/repos/awslabs/tough/security-advisories/GHSA-v57p-gppj-p9vg", "state": "published", "ghsa_id": "GHSA-v57p-gppj-p9vg", "cve_id": "CVE-2026-6968", "summary": "Multiple Path Traversal Variants in awslabs/tough", "published_at": "2026-04-24T19:57:26Z", "updated_at": "2026-04-24T19:57:26Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-6968", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-6968", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Target writing escapes the intended local directory.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-AWS-TOUGH-007/", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-31641", "title": "rxrpc: Fix RxGK token loading to check bounds", "finding_id": "F-TORVALDS-LINUX-RXRPC-001", "repo": "torvalds/linux", "url": "https://github.com/advisories/GHSA-p4pm-x7ch-5mvc", "patched": "Linux kernel upstream", "status": "patched", "kind": "cve", "note": "GHSA-p4pm-x7ch-5mvc · rxrpc: Fix RxGK token loading to check bounds · Linux CNA/GHSA credit fields are empty; credit is carried by upstream patch artifacts (Author/Signed-off-by)", "cve_publication": { "id": "CVE-2026-31641", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31641", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "RxGK token loading omits required buffer bounds checks.", "source": "https://github.com/advisories/GHSA-p4pm-x7ch-5mvc", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-RXRPC-001/", "source_url": "https://github.com/advisories/GHSA-p4pm-x7ch-5mvc", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-31662", "title": "tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG", "finding_id": "F-TORVALDS-LINUX-TIPC-001", "repo": "torvalds/linux", "url": "https://github.com/advisories/GHSA-895h-4xx6-r95p", "patched": "Linux kernel upstream", "status": "patched", "kind": "cve", "note": "GHSA-895h-4xx6-r95p · Red Hat also tracks this as a kernel CVE · Linux CNA/GHSA credit fields are empty; credit is carried by upstream patch artifacts (Author/Signed-off-by)", "cve_publication": { "id": "CVE-2026-31662", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31662", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "Duplicate acknowledgements underflow bc_ackers and block later broadcasts; no memory corruption is asserted.", "source": "https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=48a5fe38772b6f039522469ee6131a67838221a8", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-TIPC-001/", "source_url": "https://github.com/advisories/GHSA-895h-4xx6-r95p", "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-5068", "finding_id": "F-ZEPHYR-BLE-001", "repo": "zephyrproject-rtos/zephyr", "url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "patched": "main PR #104913, v4.3 PR #108335; v3.7 backport pending", "status": "patched", "kind": "cve", "cvss": 7.6, "cvss_vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H", "cwe": "CWE-787", "credit": "reporter: @1seal", "note": "GHSA-qrcq-hxwj-mqxm · bt l2cap le coc remote out-of-bounds write via segment counter stored in net_buf user_data. advisory credits @1seal as reporter; main PR #104913 merged 2026-03-28 and v4.3 backport PR #108335 merged 2026-06-03; v3.7 backport #108336 remained pending at verification time and the advisory listed patched versions as none.", "classification": { "area": "memory-safety", "reason": "BLE L2CAP reassembly writes a two-byte segment counter beyond undersized buffer user data.", "source": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "resolved_url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "api_url": "https://api.github.com/repos/zephyrproject-rtos/zephyr/security-advisories/GHSA-qrcq-hxwj-mqxm", "state": "published", "ghsa_id": "GHSA-qrcq-hxwj-mqxm", "cve_id": "CVE-2026-5068", "summary": "bt: l2cap le coc: remote oob write via seg counter stored in net_buf user_data", "published_at": "2026-06-09T06:11:47Z", "updated_at": "2026-06-09T06:15:24Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-787" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-5068", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-5068", "fetched_at": "2026-09-23T20:30:40.966Z" }, "cvss_assessment": { "version": "3.1", "score": 7.6, "vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H", "assessor": "Zephyr (repository advisory)", "source_url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "observed_at": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ZEPHYR-BLE-001/", "source_url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "title": null, "disclosed": null, "layer": "memory-safety" }, { "id": "CVE-2026-48978", "finding_id": "F-ORAS-AUTH-001", "repo": "oras-project/oras-go", "url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "patched": "oras-go v2.7.0", "status": "patched", "kind": "cve", "cwe": "CWE-319, CWE-918", "credit": "@1seal credited as Analyst; advisory says reported by bugbunny.ai", "note": "GHSA-xf85-363p-868w · Bearer realm URL not validated, enabling SSRF to internal networks and TLS downgrade. maps to local F-ORAS-AUTH-001; the public advisory credits @1seal as Analyst rather than reporter.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "resolved_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "api_url": "https://api.github.com/repos/oras-project/oras-go/security-advisories/GHSA-xf85-363p-868w", "state": "published", "ghsa_id": "GHSA-xf85-363p-868w", "cve_id": "CVE-2026-48978", "summary": "Bearer realm URL not validated, enabling SSRF to internal networks and TLS downgrade", "published_at": "2026-06-11T19:39:49Z", "updated_at": "2026-06-11T19:39:49Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-319", "CWE-918" ], "credits": [ { "login": "1seal", "role": "analyst", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-48978", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-48978", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "Bearer realm URLs allow internal-network requests and TLS downgrade.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ORAS-AUTH-001/", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "title": null, "disclosed": null, "layer": "authorization" }, { "id": "CVE-2026-50151", "finding_id": "F-ORAS-LOCATION-UPLOAD-001", "repo": "oras-project/oras-go", "url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "patched": "https://github.com/oras-project/oras-go: v2.6.2", "status": "patched", "kind": "cve", "cvss": 7.5, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N", "cwe": "CWE-918", "credit": "reporter: @1seal", "note": "Public fix PR #1192; the published advisory lists v2.6.2 as patched. Reporter credit is retained in the upstream snapshot.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "resolved_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "api_url": "https://api.github.com/repos/oras-project/oras-go/security-advisories/GHSA-jxpm-75mh-9fp7", "state": "published", "ghsa_id": "GHSA-jxpm-75mh-9fp7", "cve_id": "CVE-2026-50151", "summary": "credential forwarding via unvalidated Location header in oras-go blob upload", "published_at": "2026-06-11T19:40:29Z", "updated_at": "2026-07-12T11:36:20Z", "withdrawn_at": null, "fetched_at": "2026-09-23T20:30:40.966Z", "cwes": [ "CWE-918" ], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ], "packages": [ { "name": "https://github.com/oras-project/oras-go", "ecosystem": "go", "affected": "v2.6.0", "patched": "v2.6.2" } ] }, "cve_publication": { "id": "CVE-2026-50151", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-50151", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "An unvalidated upload Location receives forwarded credentials.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ORAS-LOCATION-UPLOAD-001/", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "title": null, "disclosed": null, "layer": "authorization" }, { "id": "CVE-2026-55644", "finding_id": "F-ELEMENTX-IOS-001", "repo": "element-hq/element-x-ios", "url": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "patched": "Element X iOS 26.05.0", "status": "patched", "kind": "cve", "cvss": 7.5, "note": "GHSA-54w7-rw44-49m7 · io.element.call deeplink allowed attacker-controlled HTTPS origin inside the call WKWebView with microphone/camera permissions. PR #5515 removed in-app SPA call link handling on 2026-04-29; Element X iOS 26.05.0 released on 2026-05-06 with the security fix. versions 26.05.0+ are fixed for this deeplink issue.", "classification": { "area": "authorization", "reason": "An unchecked call-link origin can inherit the application WebView camera and microphone permissions.", "source": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "reviewed": "2026-09-21" }, "upstream": { "schema_version": "1.0", "source_url": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "resolved_url": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "api_url": "https://api.github.com/repos/element-hq/element-x-ios/security-advisories/GHSA-54w7-rw44-49m7", "state": "published", "ghsa_id": "GHSA-54w7-rw44-49m7", "cve_id": "CVE-2026-55644", "summary": "io.element.call deeplink allows attacker-controlled HTTPS origin and may grant mic/camera to that origin", "published_at": "2026-06-15T10:35:14Z", "updated_at": "2026-06-17T00:10:25Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [], "credits": [] }, "cve_publication": { "id": "CVE-2026-55644", "state": "RESERVED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-55644", "fetched_at": "2026-09-23T20:30:40.966Z" }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-ELEMENTX-IOS-001/", "source_url": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "title": null, "disclosed": null, "cwe": null, "layer": "authorization" }, { "id": "CVE-2026-48497", "finding_id": "F-ENVOY-001-002", "repo": "envoyproxy/envoy", "url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "patched": "Envoy 1.35.12, 1.36.8, 1.37.4, 1.38.2", "status": "patched", "kind": "cve", "cvss": 5.9, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H", "cwe": "CWE-480", "credit": "finder: @1seal", "note": "GHSA-j6g2-wf95-q66q · abnormal process termination in the Envoy DNS UDP filter for a 255-octet DNS query name. maps to local F-ENVOY-001-002; affected versions are <1.39 and patched versions are 1.35.12, 1.36.8, 1.37.4, and 1.38.2.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "resolved_url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "api_url": "https://api.github.com/repos/envoyproxy/envoy/security-advisories/GHSA-j6g2-wf95-q66q", "state": "published", "ghsa_id": "GHSA-j6g2-wf95-q66q", "cve_id": "CVE-2026-48497", "summary": "Abnormal process termination in DNS UDP filter", "published_at": "2026-06-23T14:08:25Z", "updated_at": "2026-06-23T14:08:25Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:07:19Z", "cwes": [ "CWE-480" ], "credits": [ { "login": "1seal", "role": "finder", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-48497", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-48497", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "availability", "reason": "A valid 255-octet DNS name violates an incorrect runtime precondition.", "source": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ENVOY-001-002/", "source_url": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "title": null, "disclosed": null, "layer": "availability" }, { "id": "CVE-2026-43334", "finding_id": "F-TORVALDS-LINUX-BT-SMP-001", "repo": "torvalds/linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "title": "Bluetooth: SMP: force responder MITM requirements before building the pairing response", "kind": "cve", "status": "patched", "patched": "Linux 7.0; stable backports listed in the CNA record; mainline d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7", "cvss": 8.8, "cvss_vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "credit": "Upstream commit author and Signed-off-by: Oleh Konko / 1seal; no credit field in the Linux CNA record.", "disclosed": "2026-05-08", "note": "CNA record verified PUBLISHED on 2026-09-23 and matched to the exact mainline fix. Upstream authorship source: https://github.com/torvalds/linux/commit/d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7. Score is the current Linux CNA CVSS v3.1, not a revision of the original report assessment.", "cve_publication": { "id": "CVE-2026-43334", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-43334", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "Bluetooth pairing can assert authenticated MITM protection without establishing it; this is a peer-authentication property.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-SMP-001/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "cwe": null, "layer": "identity" }, { "id": "CVE-2026-31773", "finding_id": "F-TORVALDS-LINUX-BT-SMP-001", "repo": "torvalds/linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-31773", "title": "Bluetooth: SMP: derive legacy responder STK authentication from MITM state", "kind": "cve", "status": "patched", "patched": "Linux 7.0; stable backports listed in the CNA record; mainline 20756fec2f0108cb88e815941f1ffff88dc286fe", "cvss": 8.8, "cvss_vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "credit": "Upstream commit author and Signed-off-by: Oleh Konko / 1seal; no credit field in the Linux CNA record.", "disclosed": "2026-05-01", "note": "CNA record verified PUBLISHED on 2026-09-23 and matched to the exact mainline fix. Upstream authorship source: https://github.com/torvalds/linux/commit/20756fec2f0108cb88e815941f1ffff88dc286fe. Score is the current Linux CNA CVSS v3.1, not a revision of the original report assessment.", "cve_publication": { "id": "CVE-2026-31773", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31773", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "identity", "reason": "The legacy STK authentication flag must reflect the actual MITM state, not merely the requested protection level.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-SMP-001/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-31773", "cwe": null, "layer": "identity" }, { "id": "CVE-2026-31771", "finding_id": "F-TORVALDS-LINUX-BT-HCI-001", "repo": "torvalds/linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-31771", "title": "Bluetooth: hci_event: move wake reason storage into validated event handlers", "kind": "cve", "status": "patched", "patched": "Linux 7.0; stable backports listed in the CNA record; mainline 2b2bf47cd75518c36fa2d41380e4a40641cc89cd", "cvss": 8.1, "cvss_vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H", "credit": "Upstream commit author and Signed-off-by: Oleh Konko / 1seal; no credit field in the Linux CNA record.", "disclosed": "2026-05-01", "note": "CNA record verified PUBLISHED on 2026-09-23 and matched to the exact mainline fix. Upstream authorship source: https://github.com/torvalds/linux/commit/2b2bf47cd75518c36fa2d41380e4a40641cc89cd. Score is the current Linux CNA CVSS v3.1, not a revision of the original report assessment.", "cve_publication": { "id": "CVE-2026-31771", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-31771", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "memory-safety", "reason": "HCI event handling lacks required buffer bounds validation.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-31771", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-HCI-001/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-31771", "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-50162", "finding_id": "F-ORAS-SYMLINK-WRITE-001", "repo": "oras-project/oras-go", "url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "title": "file store write outside workingDir via symlink traversal in oras-go", "kind": "cve", "status": "patched", "patched": "CVE record: 2.6.1; GHSA: 2.6.2 (conflicting version metadata)", "cwe": "CWE-73", "credit": "reporter: @1seal (accepted, repository GHSA)", "disclosed": "2026-07-17", "note": "CVE record verified PUBLISHED on 2026-09-23. Restored after anonymous access and publication were confirmed; previously hidden while unpublished. CNA and GHSA disagree on the patched version. CVE publication was 2026-07-17; repository GHSA publication was 2026-06-11. Fix commit cc323e564d90c6b5b4bdd71d3c8d2ee2713b37e5.", "upstream": { "schema_version": "1.0", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "resolved_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "api_url": "https://api.github.com/repos/oras-project/oras-go/security-advisories/GHSA-8xwf-rjm4-xvhv", "state": "published", "ghsa_id": "GHSA-8xwf-rjm4-xvhv", "cve_id": "CVE-2026-50162", "summary": "file store write outside workingDir via symlink traversal in oras-go", "published_at": "2026-06-11T19:40:07Z", "updated_at": "2026-07-12T11:36:01Z", "withdrawn_at": null, "fetched_at": "2026-09-23T18:29:06Z", "cwes": [], "credits": [ { "login": "1seal", "role": "reporter", "state": "accepted" } ] }, "cve_publication": { "id": "CVE-2026-50162", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-50162", "fetched_at": "2026-09-23T20:30:40.966Z" }, "classification": { "area": "authorization", "reason": "A symlink permits file-store writes outside workingDir.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "reviewed": "2026-09-24" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-ORAS-SYMLINK-WRITE-001/", "source_url": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "layer": "authorization" }, { "id": "CVE-2026-80799", "finding_id": "F-TORVALDS-LINUX-NFC-001", "repo": "torvalds/linux", "url": "https://www.cve.org/CVERecord?id=CVE-2026-80799", "title": "NFC LLCP TLV parsers: missing bounds checks and offset wrap", "kind": "cve", "status": "patched", "patched": "Linux 7.3-rc1; stable fixes include 7.2.1, 7.1.11, 6.18.47, 6.12.106, 6.6.154, 6.1.185, 5.15.218 and 5.10.267; consult the Linux CNA record for affected ranges and other branches.", "credit": "Earlier public report and proposed patch: Oleh Konko / 1seal. Merged patch author: Muhammad Bilal. No reporter credit in the Linux CNA record.", "disclosed": "2026-03-26", "note": "Published CVE-2026-80799 matches the LLCP parser checks in the earlier public patch quoted at https://lists.openwall.net/netdev/2026/03/26/440. Final merged fix: https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net/+/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911. This records the earlier contribution separately from the final patch; sole discovery, final patch authorship and causation by our report are not claimed. CNA publication: 2026-09-04. No CNA CVSS assessment is recorded.", "classification": { "area": "memory-safety", "reason": "The LLCP TLV parsers read headers and payloads without required buffer bounds checks.", "source": "https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net/+/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911", "reviewed": "2026-10-07" }, "guidance": { "title": "Linux NFC: LLCP TLV parser bounds", "conditions": "Receiving malformed NFC LLCP data can reach missing header and payload bounds checks.", "action": "Check your distribution's kernel backports against the Linux CNA record; update to a supported fixed kernel. The earlier 1seal proposal and the final merged patch have separate authorship.", "reviewed": "2026-10-07" }, "cve_publication": { "id": "CVE-2026-80799", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-80799", "fetched_at": "2026-10-06T22:17:09Z" }, "related_sources": [ { "label": "Earlier Oleh Konko report and proposed patch", "url": "https://lists.openwall.net/netdev/2026/03/26/440" }, { "label": "Merged fix by Muhammad Bilal", "url": "https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net/+/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911" }, { "label": "Linux CNA record", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/80xxx/CVE-2026-80799.json" } ], "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-NFC-001/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-80799", "cwe": null, "layer": "memory-safety" }, { "id": "CVE-2026-6450", "finding_ids": [ "F-WOLFSSL-CRL-001", "F-WOLFSSL-CRL-SCOPE-COLLAPSE-001" ], "repo": "wolfSSL/wolfssl", "url": "https://www.cve.org/CVERecord?id=CVE-2026-6450", "title": "wolfSSL CRL critical extension bypass", "kind": "cve", "status": "patched", "patched": "wolfSSL 5.9.2; affected 4.3.0 through 5.9.1", "cvss": 1.0, "cvss_vector": "CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N", "credit": "wolfSSL CNA finder credit: Oleh Konko (@1seal). Fix PR #10239 opened by @gasbytes; code authorship is not claimed.", "disclosed": "2026-06-25", "note": "The published CNA record references the same PR #10239 already recorded under F-WOLFSSL-CRL-001. F-WOLFSSL-CRL-SCOPE-COLLAPSE-001 is an alternate ID for that result, not a second independent defect. wolfSSL 5.9.2 release notes confirm the fix and reporter credit: https://github.com/wolfSSL/wolfssl/blob/v5.9.2-stable/ChangeLog.md. The LOW 1.0 assessment is the wolfSSL CNA assessment, separate from any original report assessment.", "cvss_assessment": { "version": "4.0", "score": 1.0, "vector": "CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N", "assessor": "wolfSSL CNA", "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/6xxx/CVE-2026-6450.json", "observed_at": "2026-10-07" }, "classification": { "area": "identity", "reason": "Unknown critical CRL extensions are not rejected as required.", "source": "https://github.com/wolfSSL/wolfssl/pull/10239", "reviewed": "2026-09-24" }, "guidance": { "title": "wolfSSL: reject unknown critical CRL extensions", "conditions": "CRL support must be enabled and the crafted CRL must have a trusted signature.", "action": "Use wolfSSL 5.9.2 or later with the PR #10239 fix. The published CNA rating is LOW (CVSS 4.0: 1.0).", "reviewed": "2026-10-07" }, "cve_publication": { "id": "CVE-2026-6450", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-6450", "fetched_at": "2026-10-06T22:17:09Z" }, "related_sources": [ { "label": "wolfSSL 5.9.2 release notes and reporter credit", "url": "https://github.com/wolfSSL/wolfssl/blob/v5.9.2-stable/ChangeLog.md" }, { "label": "Existing fix PR #10239", "url": "https://github.com/wolfSSL/wolfssl/pull/10239" }, { "label": "wolfSSL CNA record", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/6xxx/CVE-2026-6450.json" } ], "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-CRL-001/", "source_url": "https://www.cve.org/CVERecord?id=CVE-2026-6450", "cwe": null, "layer": "identity" }, { "id": "GHSA-hf3w-6hpw-qp67", "finding_id": "F-GRPC-001", "repo": "grpc/grpc", "url": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "kind": "ghsa", "status": "patched", "title": "gRPC-C++: enforce message size while decompressing", "patched": "gRPC 1.83.1 and 1.82.2; keep the default message_size_refactoring experiment enabled", "severity": "high", "source_reviewed": "2026-10-07", "credit": "Public 1seal reporter credit and a causal link to the matching upstream fix are not established. Decompression patch author: Tanvi Jagtap.", "note": "Only the unbounded-decompression cause matches F-GRPC-001; the advisory also covers two other OOM causes, which are not attributed to this report. The vendor rates the complete advisory HIGH and records no CVE or CVSS score. The earlier report attachment used a separate model, not a running gRPC server. The matching public patch bounds allocation during decompression; the fix is enabled by default and can be disabled via the message_size_refactoring experiment override.", "classification": { "area": "availability", "reason": "Decompression can allocate beyond the configured maximum message length before rejecting the RPC.", "source": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "reviewed": "2026-10-07" }, "related_sources": [ { "label": "Decompression allocation-limit patch", "url": "https://github.com/grpc/grpc/commit/6d54d63fb13c91e7f28987253f8f679a5521f1a3" }, { "label": "Verified fixed 1.83.1 decompression source", "url": "https://github.com/grpc/grpc/blob/v1.83.1/src/core/lib/compression/message_compress.cc" } ], "upstream": { "schema_version": "1.0", "source_url": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "resolved_url": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "api_url": "https://api.github.com/repos/grpc/grpc/security-advisories/GHSA-hf3w-6hpw-qp67", "state": "published", "ghsa_id": "GHSA-hf3w-6hpw-qp67", "cve_id": null, "summary": "Multiple heap memory exhaustion (OOM) bug fixes in gRPC-C++", "published_at": "2026-08-28T04:41:49Z", "updated_at": "2026-08-28T04:41:49Z", "withdrawn_at": null, "fetched_at": "2026-10-07T01:10:09Z", "cwes": [ "CWE-400" ], "credits": [], "packages": [ { "name": "github.com/grpc/grpc", "ecosystem": "c++, python, ruby, objective-c, php", "affected": "<= 1.83.0", "patched": "1.83.1 and 1.82.2" } ] }, "record_type": "advisory", "counted": true, "advisory_type": "ghsa", "canonical_url": "https://1seal.org/research/findings/F-GRPC-001/", "source_url": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "disclosed": null, "cwe": null, "layer": "availability" }, { "id": "CVE-2026-107446", "finding_id": "F-OVERLAYBD-001-002", "repo": "containerd/overlaybd", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/107xxx/CVE-2026-107446.json", "title": "OverlayBD LSMT index size integer overflow causes out-of-bounds heap access", "patched": "Public code fix merged; fixed release not independently confirmed", "status": "fixed in public code; release unconfirmed", "kind": "cve", "cvss": 6.8, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H", "cvss_assessment": { "version": "3.1", "score": 6.8, "vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H", "assessor": "MITRE CVE record", "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/107xxx/CVE-2026-107446.json", "observed_at": "2026-10-08" }, "submitted": "2026-03-05", "note": "CVE published on 8 October 2026 for containerd overlaybd through 1.0.18: integer overflow in do_load_index when loading LSMT index metadata can cause out-of-bounds heap access when an untrusted registry blob is used with multiple overlaybd-backed containers. This is the existing researcher report F-OVERLAYBD-001-002, not an additional finding. The CVE references public index-size validation PR #438, merged on 18 August 2026. A fixed release has not been independently confirmed. The public CVE record does not include a reporter credit; the report mapping is researcher-confirmed, and the vendor patch is not attributed to 1seal.", "classification": { "area": "memory-safety", "reason": "Untrusted LSMT index metadata can overflow index_bytes and cause out-of-bounds heap access.", "source": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/107xxx/CVE-2026-107446.json", "reviewed": "2026-10-08" }, "related_sources": [ { "label": "Public index-size validation PR", "url": "https://github.com/containerd/overlaybd/pull/438" }, { "label": "CVE-referenced public commit", "url": "https://github.com/containerd/overlaybd/commit/a536e3341c82517268b5ce32375b36faecb1fb40" } ], "cve_publication": { "id": "CVE-2026-107446", "state": "PUBLISHED", "source_url": "https://cveawg.mitre.org/api/cve-id/CVE-2026-107446", "fetched_at": "2026-10-08T09:58:49.014232Z" }, "record_type": "advisory", "counted": true, "advisory_type": "cve", "canonical_url": "https://1seal.org/research/findings/F-OVERLAYBD-001-002/", "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/107xxx/CVE-2026-107446.json", "disclosed": null, "cwe": null, "layer": "memory-safety" } ], "advisories_detailed": [ { "id": "1SEAL-2026-011", "guidance": { "title": "Linux Bluetooth: pairing without MITM protection", "conditions": "Legacy Bluetooth pairing can satisfy BT_SECURITY_HIGH without authenticated MITM protection.", "action": "Check your kernel vendor's backports for both linked commits. A mainline fix does not establish the state of your distribution.", "reviewed": "2026-09-25" }, "finding_id": "F-TORVALDS-LINUX-BT-SMP-001", "repo": "torvalds/linux", "url": "/research/advisories/1SEAL-2026-011", "title": "Linux Bluetooth SMP legacy pairing can satisfy BT_SECURITY_HIGH without MITM", "severity": "high", "cvss": 7.1, "cvss_vector": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N", "cwe": "CWE-287", "patched": "mainline commits d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7 and 20756fec2f0108cb88e815941f1ffff88dc286fe", "status": "patched", "cve": "CVE-2026-43334 / CVE-2026-31773", "disclosed": "2026-04-04", "classification": { "area": "identity", "reason": "Bluetooth pairing can assert authenticated MITM protection without establishing it; this write-up describes the same peer-authentication gap.", "source": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-SMP-001/", "source_url": "/research/advisories/1SEAL-2026-011/", "layer": "identity" }, { "id": "1SEAL-2026-010", "guidance": { "title": "UEFI firmware parser: Tiano buffer writes", "conditions": "Parsing an untrusted firmware image can reach out-of-bounds writes in MakeTable or ReadCLen.", "action": "Check the installed package for the linked Tiano bounds checks. Release metadata conflicts: CVE records name 1.14; repository advisories name 1.13. Do not resolve that discrepancy from the version number alone.", "finding_titles": { "F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003": "UEFI firmware parser: ReadCLen heap write", "F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002": "UEFI firmware parser: MakeTable stack write" }, "reviewed": "2026-09-25" }, "finding_ids": [ "F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003", "F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002" ], "repo": "theopolis/uefi-firmware-parser", "url": "/research/advisories/1SEAL-2026-010", "title": "Two critical out-of-bounds writes in the imported Tiano decompressor", "severity": "critical", "cvss": null, "cvss_vector": null, "cwe": "CWE-787", "patched": "CVE records: 1.14; repository GHSAs: 1.13 (conflicting version metadata)", "status": "patched", "cve": "CVE-2026-54333 / CVE-2026-54334", "disclosed": "2026-03-29", "note": "Subsequent CVEs verified PUBLISHED on 2026-09-23: MakeTable is CVE-2026-54333; ReadCLen is CVE-2026-54334. The original write-up retains its dated observations.", "classification": { "area": "memory-safety", "reason": "Tiano ReadCLen writes outside the intended buffer. Tiano MakeTable writes outside the intended buffer.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003/", "source_url": "/research/advisories/1SEAL-2026-010/", "layer": "memory-safety" }, { "id": "1SEAL-2026-009", "guidance": { "title": "OpenSSL: unauthorized OCSP responders", "conditions": "OpenSSL 3.6 stapled OCSP verification can accept a response from an unauthorized certificate supplied in the peer chain.", "action": "Check that your build includes the recorded master or openssl-3.6 fix. A released version is not established by this write-up; PR #30323 itself was closed without merge.", "reviewed": "2026-09-25" }, "finding_id": "F-OPENSSL-OCSP-001", "repo": "openssl/openssl", "url": "/research/advisories/1SEAL-2026-009", "title": "OpenSSL 3.6 stapled OCSP verification can accept unauthorized responders from the peer chain", "severity": "high", "cvss": null, "cvss_vector": null, "cwe": "CWE-295", "patched": "master and openssl-3.6 fixes published", "status": "patched", "cve": null, "disclosed": "2026-03-29", "classification": { "area": "authorization", "reason": "Stapled OCSP verification accepts an unauthorized delegated responder.", "source": "/research/advisories/1SEAL-2026-009", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-OCSP-001/", "source_url": "/research/advisories/1SEAL-2026-009/", "layer": "authorization" }, { "id": "1SEAL-2026-008", "guidance": { "title": "Telegram iOS: bridge exposed to iframes", "conditions": "A third-party iframe in a bot Web App can reach a bridge intended for the main frame.", "action": "Use a version containing the release-12.4 main-frame checks. The source-branch evidence does not verify rollout to every installed app.", "reviewed": "2026-09-25" }, "finding_id": "F-TELEGRAM-WEBAPP-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "/research/advisories/1SEAL-2026-008", "title": "Telegram iOS Web App bridge exposed to third-party iframes", "severity": "medium", "cvss": null, "cvss_vector": null, "cwe": "CWE-863, CWE-346", "patched": "release-12.4", "status": "patched", "cve": null, "disclosed": "2026-03-29", "classification": { "area": "authorization", "reason": "A subframe can reach a bridge intended for the main frame.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/c5a0ad267cbd2a61a0d4548490f6af5521fa55df", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-WEBAPP-001/", "source_url": "/research/advisories/1SEAL-2026-008/", "layer": "authorization" }, { "id": "1SEAL-2026-007", "guidance": { "title": "Telegram iOS: TL parsing over-read", "conditions": "Malformed TL data reaches a bounds check whose operator precedence permits a heap buffer over-read.", "action": "Use a version containing the release-12.4 bounds-check correction. The source-branch evidence does not verify rollout to every installed app.", "reviewed": "2026-09-25" }, "finding_id": "F-TELEGRAM-TL-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "/research/advisories/1SEAL-2026-007", "title": "heap buffer over-read in TL deserialization from operator precedence bug", "severity": "medium", "cvss": 5.3, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N", "cwe": "CWE-125", "patched": "release-12.4", "status": "patched", "cve": null, "disclosed": "2026-03-29", "classification": { "area": "memory-safety", "reason": "TL parsing can read beyond an input buffer.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-TL-001/", "source_url": "/research/advisories/1SEAL-2026-007/", "layer": "memory-safety" }, { "id": "1SEAL-2026-006", "guidance": { "title": "BuildKit: ContainerID path escape", "conditions": "An attacker-controlled gateway frontend on a runc worker can use ContainerID paths to escape the executor root.", "action": "Upgrade affected BuildKit deployments to v0.28.1 or later; check that the worker actually runs the updated binary.", "reviewed": "2026-09-25" }, "finding_id": "F-BUILDKIT-001-001", "repo": "moby/buildkit", "url": "/research/advisories/1SEAL-2026-006", "title": "ContainerID path traversal in gateway frontend can escape runc executor root", "severity": "high", "cvss": 8.4, "cvss_vector": "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H", "cwe": "CWE-22", "patched": "v0.28.1+", "status": "patched", "cve": "CVE-2026-33747", "ghsa": "GHSA-4c29-8rgm-jvjj", "disclosed": "2026-03-25", "classification": { "area": "authorization", "reason": "ContainerID traversal escapes the executor root.", "source": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-BUILDKIT-001-001/", "source_url": "/research/advisories/1SEAL-2026-006/", "layer": "authorization" }, { "id": "1SEAL-2026-002", "guidance": { "title": "AWS-LC: CommonName constraint bypasses", "conditions": "A wildcard or Unicode CommonName can bypass name constraints when hostname verification falls back to CN without a DNS name SAN.", "action": "Check the package-specific AWS advisories for fixed versions. Disabling CN fallback avoids this path; do not apply the AWS-LC version number to aws-lc-sys.", "finding_titles": { "F-AWS-LC-NAMECONSTRAINTS-001": "AWS-LC: wildcard CommonName constraint bypass", "F-AWS-LC-NAMECONSTRAINTS-002": "AWS-LC: Unicode CommonName constraint bypass" }, "reviewed": "2026-09-25" }, "finding_ids": [ "F-AWS-LC-NAMECONSTRAINTS-001", "F-AWS-LC-NAMECONSTRAINTS-002" ], "repo": "aws/aws-lc", "url": "/research/advisories/1SEAL-2026-002", "title": "Name Constraints bypass via CommonName fallback", "severity": "high", "cvss": 7.4, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N", "cwe": "CWE-295", "patched": "AWS advisories: AWS-LC 1.71.0; aws-lc-sys 0.39.0", "status": "patched", "cve": "AWS CNA: not in scope", "certcc": "VRF#26-03-LDFDW", "disclosed": "2026-03-19", "classification": { "area": "identity", "reason": "Wildcard or Unicode common names bypass the certificate name constraints governing which identities the CA may certify.", "source": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-AWS-LC-NAMECONSTRAINTS-001/", "source_url": "/research/advisories/1SEAL-2026-002/", "layer": "identity" }, { "id": "1SEAL-2026-001", "guidance": { "title": "AWS event-stream: decoder buffer write", "conditions": "A client processing attacker-controlled event-stream headers can reach an out-of-bounds write in the streaming decoder.", "action": "Upgrade aws-c-event-stream to v0.6.0 or later and affected AWS SDK for C++ builds to the vendor's fixed version below. Check lock files as well: the AWS Common Runtime can pin an older version as a transitive dependency.", "reviewed": "2026-09-25" }, "finding_id": "F-AWS-EVENT-STREAM-001", "repo": "awslabs/aws-c-event-stream", "url": "/research/advisories/1SEAL-2026-001", "title": "remote out-of-bounds write in streaming decoder", "severity": "high", "cvss": 8.1, "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H", "cwe": "CWE-787", "patched": "v0.6.0", "status": "patched", "cve": "CVE-2026-5190", "disclosed": "2026-03-17", "classification": { "area": "memory-safety", "reason": "The streaming decoder writes beyond its header-name buffer; this is another record of the same AWS event-stream finding.", "source": "https://1seal.org/research/advisories/1SEAL-2026-001", "reviewed": "2026-09-21" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-AWS-EVENT-STREAM-001/", "source_url": "/research/advisories/1SEAL-2026-001/", "layer": "memory-safety" }, { "id": "1SEAL-2026-003", "guidance": { "title": "Tekton: git resolver path traversal", "conditions": "A tenant able to create requests using the git resolver can read files accessible to the resolver pod, including its credentials.", "action": "Use the listed patched release for your branch. Until updated, restrict access to the git resolver and reduce its service-account permissions. The upstream broad affected range overlaps its own patched list.", "reviewed": "2026-09-25" }, "finding_id": "F-TEKTON-001-001", "repo": "tektoncd/pipeline", "url": "/research/advisories/1SEAL-2026-003", "title": "path traversal in git resolver — tenant to cluster-wide secret access", "severity": "critical", "cvss": 9.6, "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N", "cwe": "CWE-22", "patched": "v1.0.1, v1.3.3, v1.6.1, v1.9.2, v1.10.2", "status": "patched", "cve": "CVE-2026-33211", "ghsa": "GHSA-j5q5-j9gm-2w5c", "disclosed": "2026-03-18", "classification": { "area": "authorization", "reason": "Git resolver traversal reaches files beyond the tenant's intended root.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TEKTON-001-001/", "source_url": "/research/advisories/1SEAL-2026-003/", "layer": "authorization" }, { "id": "1SEAL-2026-005", "guidance": { "title": "Ledger Bitcoin app: Merkle binding bypass", "conditions": "A malicious host interacting with the signing flow can bypass a reported Merkle preimage integrity check.", "action": "Check for the recorded commit in the app build you use. No fixed app release is recorded here; a code fix is not proof that your device has received it.", "reviewed": "2026-09-25" }, "finding_id": "F-LEDGER-BTC-MERKLE-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-02" }, "repo": "LedgerHQ/app-bitcoin", "url": "/research/advisories/1SEAL-2026-005", "title": "signing-path integrity gate bypass via merkle preimage binding break", "severity": "high", "cvss": null, "cvss_vector": "CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N", "cwe": "CWE-825", "patched": "commit 0586ab2", "status": "patched", "cve": null, "disclosed": "2026-03-17", "classification": { "area": "integrity", "reason": "Merkle preimage validation fails to bind the signing-path data.", "source": "/research/advisories/1SEAL-2026-005", "reviewed": "2026-09-24" }, "record_type": "1seal", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-MERKLE-001/", "source_url": "/research/advisories/1SEAL-2026-005/", "layer": "integrity" } ], "security_prs": [ { "finding_id": "F-COSIGN-003", "repo": "sigstore/cosign", "number": 4653, "url": "https://github.com/sigstore/cosign/pull/4653", "title": "reject malformed ReplaceOp payloads without a panic", "status": "merged", "disclosed": "2026-01-22", "note": "researcher-authored PR by @1seal, merged as c836f7a753724815eb5721ddaa227163971c12c0. Replaces an unchecked string assertion with validation and adds regression tests. This is an authored security contribution, not a separately confirmed CVE or a vendor-authored fix. Release inclusion was not independently checked.", "classification": { "area": "availability", "reason": "An unchecked type assertion on a malformed replacement payload can terminate the operation with a panic.", "source": "https://github.com/sigstore/cosign/pull/4653", "reviewed": "2026-09-23" }, "pr_evidence": { "source_url": "https://github.com/sigstore/cosign/pull/4653", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-COSIGN-003/", "source_url": "https://github.com/sigstore/cosign/pull/4653", "cwe": null, "layer": "availability" }, { "repo": "caddyserver/website", "number": 529, "url": "https://github.com/caddyserver/website/pull/529", "title": "docs: clarify file_server hide case-sensitivity", "category": "hardening", "why": "documents that hide comparisons are case-sensitive; on case-insensitive filesystems, differently-cased request paths may still resolve to the same on-disk path, so hide should not be treated as a security boundary for sensitive paths.", "finding_id": "F-CADDY-FILESERVER-HIDE-CASE-001", "submitted": "2026-03-04", "status": "merged", "classification": { "area": "authorization", "reason": "The documented hide-rule boundary depends on filesystem case behavior.", "source": "https://github.com/caddyserver/website/pull/529", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/caddyserver/website/pull/529", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CADDY-FILESERVER-HIDE-CASE-001/", "source_url": "https://github.com/caddyserver/website/pull/529", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "google/certificate-transparency-go", "number": 1754, "url": "https://github.com/google/certificate-transparency-go/pull/1754", "title": "Cap request body size in submission proxy", "category": "hardening", "why": "caps request body size in the submission proxy to reduce resource exhaustion / DoS risk.", "finding_id": "F-CTGO-S2A-001", "submitted": "2026-01-26", "status": "merged", "classification": { "area": "availability", "reason": "An HTTP request body is not bounded before processing.", "source": "https://github.com/google/certificate-transparency-go/pull/1754", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/google/certificate-transparency-go/pull/1754", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CTGO-S2A-001/", "source_url": "https://github.com/google/certificate-transparency-go/pull/1754", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "goharbor/website", "number": 706, "url": "https://github.com/goharbor/website/pull/706", "title": "docs: clarify proxy cache trust boundary for upstream token-service discovery", "category": "hardening", "why": "clarifies the proxy cache trust boundary to reduce the risk of misconfiguration around token-service discovery.", "finding_id": "F-HARBOR-REALM-001", "submitted": "2026-01-31", "status": "merged", "classification": { "area": "authorization", "reason": "Documentation clarifies which upstream token-service endpoints may receive registry credentials; this is trust-boundary guidance, not a code fix.", "source": "https://github.com/goharbor/website/pull/706", "reviewed": "2026-09-21" }, "pr_evidence": { "source_url": "https://github.com/goharbor/website/pull/706", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-HARBOR-REALM-001/", "source_url": "https://github.com/goharbor/website/pull/706", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "caddyserver/caddy", "number": 7469, "url": "https://github.com/caddyserver/caddy/pull/7469", "title": "acmeserver: warn when policy rules unset", "category": "hardening", "why": "mitigates policy misconfiguration risk by warning when policy rules are unset.", "finding_id": "F-CADDY-ACME-POLICY-001", "submitted": "2026-02-11", "status": "merged", "classification": { "area": "authorization", "reason": "The warning concerns an unset certificate issuance permission policy; this classifies authorization guidance, not a newly confirmed exploit.", "source": "https://github.com/caddyserver/caddy/pull/7469", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/caddyserver/caddy/pull/7469", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CADDY-ACME-POLICY-001/", "source_url": "https://github.com/caddyserver/caddy/pull/7469", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "caddyserver/certmagic", "number": 378, "url": "https://github.com/caddyserver/certmagic/pull/378", "title": "More validation of delegated OCSP responders", "category": "fix", "why": "rejects forged Good OCSP responses signed by same-issuer responder certificates that lack delegated OCSPSigning authorization under RFC 6960 section 4.2.2.2. public PR #378 merged on 2026-04-24.", "finding_id": "F-CADDY-CERTMAGIC-OCSP-001", "submitted": "2026-04-20", "status": "merged", "classification": { "area": "authorization", "reason": "Delegated OCSP responders require explicit signing authorization.", "source": "https://github.com/caddyserver/certmagic/pull/378", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/caddyserver/certmagic/pull/378", "author": "mholt", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CADDY-CERTMAGIC-OCSP-001/", "source_url": "https://github.com/caddyserver/certmagic/pull/378", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "caddyserver/certmagic", "number": 383, "url": "https://github.com/caddyserver/certmagic/pull/383", "title": "ocsp: add delegated responder authorization regression test", "category": "testing", "why": "adds regression coverage for the delegated OCSP responder authorization path fixed for F-CADDY-CERTMAGIC-OCSP-001, including rejection of same-issuer non-OCSPSigning responders.", "finding_id": "F-CADDY-CERTMAGIC-OCSP-001", "submitted": "2026-05-12", "status": "merged", "classification": { "area": "authorization", "reason": "Delegated OCSP responders require explicit signing authorization.", "source": "https://github.com/caddyserver/certmagic/pull/378", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/caddyserver/certmagic/pull/383", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CADDY-CERTMAGIC-OCSP-001/", "source_url": "https://github.com/caddyserver/certmagic/pull/383", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "google/certificate-transparency-go", "number": 1755, "url": "https://github.com/google/certificate-transparency-go/pull/1755", "title": "set explicit http server timeouts", "category": "hardening", "why": "prevents hangs via slow-client / slowloris-style connections.", "finding_id": "F-CTGO-TIMEOUT-001", "patched": "v1.3.3", "submitted": "2026-01-31", "status": "merged", "classification": { "area": "availability", "reason": "Missing timeouts leave HTTP operations unbounded.", "source": "https://github.com/google/certificate-transparency-go/pull/1755", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/google/certificate-transparency-go/pull/1755", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CTGO-TIMEOUT-001/", "source_url": "https://github.com/google/certificate-transparency-go/pull/1755", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/cosign", "number": 4652, "url": "https://github.com/sigstore/cosign/pull/4652", "title": "remote crash in rekor response handling via unsafe e.body.(string) type assertion", "category": "fix", "why": "prevents remote crash via malformed rekor responses.", "finding_id": "F-COSIGN-005", "submitted": "2026-01-20", "status": "merged", "classification": { "area": "availability", "reason": "An unexpected body type reaches an unchecked string assertion.", "source": "https://github.com/sigstore/cosign/pull/4652", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/cosign/pull/4652", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-COSIGN-005/", "source_url": "https://github.com/sigstore/cosign/pull/4652", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/cosign", "number": 4651, "url": "https://github.com/sigstore/cosign/pull/4651", "title": "remote crash in policy evaluation via unsafe attestation payload type assertion", "category": "fix", "why": "prevents remote crash via malformed attestation payloads.", "finding_id": "F-COSIGN-006", "submitted": "2026-01-20", "status": "merged", "classification": { "area": "availability", "reason": "Malformed attestation input reaches an unchecked type assertion.", "source": "https://github.com/sigstore/cosign/pull/4651", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/cosign/pull/4651", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-COSIGN-006/", "source_url": "https://github.com/sigstore/cosign/pull/4651", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/sigstore-go", "number": 567, "url": "https://github.com/sigstore/sigstore-go/pull/567", "title": "bundle parsing dos via unbounded tlogentries", "category": "fix proposal", "why": "Proposed a cap during bundle parsing; this PR closed without merge on 2026-05-07. A narrower follow-up, #630 by @tonghuaroot, merged on 2026-05-27 and explicitly references #567. It caps decoded tlog entry count before per-entry parsing, but after protojson.Unmarshal; initial JSON decoding allocations remain outside that bound.", "finding_id": "F-SIG-GO-000-001", "submitted": "2026-01-17", "status": "closed unmerged", "classification": { "area": "availability", "reason": "An unbounded transparency-log entry set consumes excessive resources.", "source": "https://github.com/sigstore/sigstore-go/pull/567", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/sigstore-go/pull/567", "author": "1seal", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "related_sources": [ { "label": "Merged follow-up #630 (different author; narrower scope)", "url": "https://github.com/sigstore/sigstore-go/pull/630" } ], "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-GO-000-001/", "source_url": "https://github.com/sigstore/sigstore-go/pull/567", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/sigstore-go", "number": 566, "url": "https://github.com/sigstore/sigstore-go/pull/566", "title": "nil pointer dereference in publickey() via malformed pem", "category": "fix", "why": "prevents crash on malformed pem input.", "finding_id": "F-SIG-GO-004", "submitted": "2026-01-17", "status": "merged", "classification": { "area": "availability", "reason": "Malformed PEM input reaches a nil dereference.", "source": "https://github.com/sigstore/sigstore-go/pull/566", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/sigstore-go/pull/566", "author": "bobcallaway", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-GO-004/", "source_url": "https://github.com/sigstore/sigstore-go/pull/566", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/cosign", "number": 4649, "url": "https://github.com/sigstore/cosign/pull/4649", "title": "remote crash in online tlog verification via nil pointer dereference in verifytlogentryoffline", "category": "fix", "why": "prevents remote crash in online tlog verification.", "finding_id": "F-COSIGN-004", "submitted": "2026-01-17", "status": "merged", "classification": { "area": "availability", "reason": "A nil transparency-log entry reaches an unchecked access.", "source": "https://github.com/sigstore/cosign/pull/4649", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/cosign/pull/4649", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-COSIGN-004/", "source_url": "https://github.com/sigstore/cosign/pull/4649", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "sigstore/timestamp-authority", "number": 1277, "url": "https://github.com/sigstore/timestamp-authority/pull/1277", "title": "timestamp response verification accepts revoked tsa certificate (no crl/ocsp checking)", "category": "fix", "why": "prevents accepting revoked tsa certificates (crl/ocsp).", "finding_id": "F-TSA-001-002", "submitted": "2026-01-10", "status": "merged", "classification": { "area": "identity", "reason": "Timestamp certificate validation does not reject the recorded revocation case.", "source": "https://github.com/sigstore/timestamp-authority/pull/1277", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/timestamp-authority/pull/1277", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TSA-001-002/", "source_url": "https://github.com/sigstore/timestamp-authority/pull/1277", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "sigstore/timestamp-authority", "number": 1276, "url": "https://github.com/sigstore/timestamp-authority/pull/1276", "title": "ntp drift does not gate timestamp issuance", "category": "hardening", "why": "mitigates time manipulation risk via excessive ntp drift.", "finding_id": "F-SIG-040-001", "submitted": "2026-01-10", "status": "merged", "classification": { "area": "integrity", "reason": "Clock-drift evidence is not applied as an issuance gate.", "source": "https://github.com/sigstore/timestamp-authority/pull/1276", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/timestamp-authority/pull/1276", "author": "kommendorkapten", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-040-001/", "source_url": "https://github.com/sigstore/timestamp-authority/pull/1276", "disclosed": null, "cwe": null, "layer": "integrity" }, { "repo": "sigstore/sigstore-go", "number": 562, "url": "https://github.com/sigstore/sigstore-go/pull/562", "title": "tlog entry validation fail-open (rekor v2 protojson parsing)", "category": "fix", "why": "prevents fail-open behavior on malformed tlog entries.", "finding_id": "F-SIG-004-002", "submitted": "2026-01-10", "status": "merged", "classification": { "area": "integrity", "reason": "A log-data decoding failure is not handled fail-closed during verification.", "source": "https://github.com/sigstore/sigstore-go/pull/562", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/sigstore-go/pull/562", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-004-002/", "source_url": "https://github.com/sigstore/sigstore-go/pull/562", "disclosed": null, "cwe": null, "layer": "integrity" }, { "repo": "sigstore/sigstore-go", "number": 558, "url": "https://github.com/sigstore/sigstore-go/pull/558", "title": "certificate identity regex not auto-anchored enables identity policy bypass", "category": "fix", "why": "prevents identity policy bypass via unanchored regex matching.", "finding_id": "F-SIG-016-001", "submitted": "2026-01-10", "status": "merged", "classification": { "area": "identity", "reason": "An unanchored identity regex accepts a partial certificate-identity match.", "source": "https://github.com/sigstore/sigstore-go/pull/558", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/sigstore-go/pull/558", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-016-001/", "source_url": "https://github.com/sigstore/sigstore-go/pull/558", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "sigstore/policy-controller", "number": 1923, "url": "https://github.com/sigstore/policy-controller/pull/1923", "title": "docs(crd): clarify ctlog:{} disables tlog verification", "category": "documentation proposal", "why": "Proposes documentation for the existing behavior of an empty ctlog configuration. This PR does not change verification behavior and is not an applied code fix.", "finding_id": "F-SIG-034-001", "submitted": "2026-01-10", "status": "open", "classification": { "area": "integrity", "reason": "Documentation describes an integrity-verification configuration boundary; the open proposal does not enforce that boundary.", "source": "https://github.com/sigstore/policy-controller/pull/1923", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/policy-controller/pull/1923", "author": "1seal", "state": "open", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-034-001/", "source_url": "https://github.com/sigstore/policy-controller/pull/1923", "disclosed": null, "cwe": null, "layer": "integrity" }, { "repo": "sigstore/cosign", "number": 4642, "url": "https://github.com/sigstore/cosign/pull/4642", "title": "rfc3161 timestamp verification accepts revoked tsa certificate (no crl/ocsp checking)", "category": "fix", "why": "prevents accepting revoked tsa certificates (crl/ocsp).", "finding_id": "F-SIG-014-001", "submitted": "2026-01-10", "status": "merged", "classification": { "area": "identity", "reason": "RFC3161 verification accepts the recorded revoked timestamp signer.", "source": "https://github.com/sigstore/cosign/pull/4642", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/sigstore/cosign/pull/4642", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-014-001/", "source_url": "https://github.com/sigstore/cosign/pull/4642", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "prometheus/prometheus", "number": 17969, "url": "https://github.com/prometheus/prometheus/pull/17969", "title": "security hardening: relabel perf/dos guard", "category": "hardening", "why": "reduces resource-exhaustion surface in relabel processing.", "finding_id": "F-PROMETHEUS-RELABEL-001", "submitted": null, "status": "merged", "classification": { "area": "availability", "reason": "Computing relabel steps in one pass removes repeated processing of preceding rules and limits amplification of work.", "source": "https://github.com/prometheus/prometheus/pull/17969", "reviewed": "2026-09-21" }, "pr_evidence": { "source_url": "https://github.com/prometheus/prometheus/pull/17969", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROMETHEUS-RELABEL-001/", "source_url": "https://github.com/prometheus/prometheus/pull/17969", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "theupdateframework/python-tuf", "number": 2903, "url": "https://github.com/theupdateframework/python-tuf/pull/2903", "finding_id": "F-TUF-PYTUF-002", "title": "feat(ngclient): require explicit bootstrap argument", "category": "hardening", "why": "prevents accidental insecure bootstrap behavior by requiring explicit bootstrap intent.", "submitted": "2026-01-25", "status": "merged", "classification": { "area": "provenance", "reason": "Explicit bootstrap makes the initial trusted metadata origin a caller decision; this is trust-root provenance hardening.", "source": "https://github.com/theupdateframework/python-tuf/pull/2903", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/theupdateframework/python-tuf/pull/2903", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TUF-PYTUF-002/", "source_url": "https://github.com/theupdateframework/python-tuf/pull/2903", "disclosed": null, "cwe": null, "layer": "provenance" }, { "repo": "openssl/openssl", "number": 30319, "url": "https://github.com/openssl/openssl/pull/30319", "finding_id": "F-OPENSSL-NC-URI-AUTHORITY-001", "title": "fix OSSL_parse_url userinfo scan to respect authority boundary", "category": "fix", "why": "prevents URI authority confusion when certificate verification reuses parsed hosts for nameConstraints decisions.", "submitted": "2026-03-09", "status": "applied upstream", "classification": { "area": "identity", "reason": "URI authority parsing misidentifies the hostname for name constraints.", "source": "https://github.com/openssl/openssl/pull/30319", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/openssl/openssl/pull/30319", "author": "1seal", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-NC-URI-AUTHORITY-001/", "source_url": "https://github.com/openssl/openssl/pull/30319", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "openssl/openssl", "number": 30323, "url": "https://github.com/openssl/openssl/pull/30323", "finding_id": "F-OPENSSL-OCSP-001", "title": "x509: reject unauthorized stapled OCSP response signers", "category": "fix", "why": "prevents accepting stapled OCSP responses signed by unauthorized responder certificates.", "submitted": "2026-03-09", "status": "applied upstream", "classification": { "area": "authorization", "reason": "Stapled OCSP verification accepts an unauthorized delegated responder.", "source": "/research/advisories/1SEAL-2026-009", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/openssl/openssl/pull/30323", "author": "1seal", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-OCSP-001/", "source_url": "https://github.com/openssl/openssl/pull/30323", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "openssl/openssl", "number": 30329, "url": "https://github.com/openssl/openssl/pull/30329", "title": "Forbid GEN_OTHERNAME SMTP UTF8 email name constraints.", "category": "fix", "why": "rejects SMTPUTF8 mailbox name constraints encoded as GEN_OTHERNAME to avoid ambiguous email name-constraint handling. public upstream commits 3eab35f and 945cc69 landed on master after PR #30329.", "finding_id": "F-OPENSSL-NC-SMTPUTF8MAILBOX-001", "submitted": "2026-03-09", "status": "applied upstream", "classification": { "area": "identity", "reason": "Unsupported email name-constraint forms must be rejected.", "source": "https://github.com/openssl/openssl/pull/30329", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/openssl/openssl/pull/30329", "author": "bob-beck", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-NC-SMTPUTF8MAILBOX-001/", "source_url": "https://github.com/openssl/openssl/pull/30329", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "hashicorp/vault", "number": 31828, "url": "https://github.com/hashicorp/vault/pull/31828", "finding_id": "F-VAULT-ACME-SSRF-001", "title": "pki/acme: reject unsafe validation targets during challenge verification", "category": "opened PR", "why": "hardens ACME validation so HTTP-01 and TLS-ALPN-01 challenge dials reject loopback, link-local, unspecified, multicast, and similar unsafe targets before outbound connections. public PR #31828 was opened from the reporter branch, approved by the Vault maintainer, and copied into vault-enterprise #12959, which merged on 2026-03-12.", "submitted": "2026-01-31", "status": "enterprise merged", "classification": { "area": "authorization", "reason": "ACME validation dials attacker-controlled DNS destinations.", "source": "https://github.com/advisories/GHSA-8r5m-3f66-qpr3", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/hashicorp/vault/pull/31828", "author": "1seal", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-VAULT-ACME-SSRF-001/", "source_url": "https://github.com/hashicorp/vault/pull/31828", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "wolfSSL/wolfssl", "number": 10239, "url": "https://github.com/wolfSSL/wolfssl/pull/10239", "title": "reject crls with unrecognized critical extensions", "category": "fix", "why": "rejects CRLs with unrecognized critical extensions per RFC 5280 section 5.2 instead of silently accepting a revocation scope-bypass condition. public PR #10239 merged on 2026-04-21.", "submitted": "2026-04-15", "status": "merged", "classification": { "area": "identity", "reason": "Unknown critical CRL extensions are not rejected as required.", "source": "https://github.com/wolfSSL/wolfssl/pull/10239", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/wolfSSL/wolfssl/pull/10239", "author": "gasbytes", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "finding_ids": [ "F-WOLFSSL-CRL-001", "F-WOLFSSL-CRL-SCOPE-COLLAPSE-001" ], "cve": "CVE-2026-6450", "patched": "wolfSSL 5.9.2", "credit": "wolfSSL CNA finder credit: Oleh Konko (@1seal). Fix PR #10239 opened by @gasbytes; code authorship is not claimed.", "note": "CVE-2026-6450 covers this existing CRL fix. The two Finding IDs identify the same result; CNA finder credit and PR authorship are separate. Published CNA CVSS 4.0: 1.0 LOW; no revision of the original report assessment.", "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-CRL-001/", "source_url": "https://github.com/wolfSSL/wolfssl/pull/10239", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "aws/aws-nitro-enclaves-sdk-c", "number": 167, "url": "https://github.com/aws/aws-nitro-enclaves-sdk-c/pull/167", "title": "cms: Reject AES-256-CBC IV with invalid length", "category": "fix", "why": "rejects malformed CMS AES-256-CBC IV lengths before decryption so short IV buffers cannot reach EVP_DecryptInit_ex unchecked.", "finding_id": "F-NITRO-IVLEN-001", "submitted": "2026-03-30", "status": "merged", "classification": { "area": "memory-safety", "reason": "Rejecting a short AES IV prevents the decrypt initializer from reading beyond the supplied buffer.", "source": "https://github.com/aws/aws-nitro-enclaves-sdk-c/pull/167", "reviewed": "2026-09-21" }, "pr_evidence": { "source_url": "https://github.com/aws/aws-nitro-enclaves-sdk-c/pull/167", "author": "mariusknaust", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NITRO-IVLEN-001/", "source_url": "https://github.com/aws/aws-nitro-enclaves-sdk-c/pull/167", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "repo": "cilium/cilium", "number": 44772, "url": "https://github.com/cilium/cilium/pull/44772", "title": "Add a warning when TLS isn't enabled for Hubble Relay", "category": "hardening", "why": "warns that Hubble Relay without TLS exposes sensitive observability data to any reachable in-cluster client outside the intended trust boundary. public PR #44772 merged on 2026-04-22 and is present in main / v1.20.0-pre.* only; not fixed for stable users in v1.19.5, v1.18.11, or v1.17.17.", "finding_id": "F-CILIUM-001-002", "submitted": "2026-03-13", "status": "merged to main/pre-release only", "credit": "Reported by @1seal", "classification": { "area": "confidentiality", "reason": "The change warns about unencrypted Hubble Relay/UI traffic; it does not itself enable TLS.", "source": "https://github.com/cilium/cilium/pull/44772", "reviewed": "2026-09-21" }, "pr_evidence": { "source_url": "https://github.com/cilium/cilium/pull/44772", "author": "ferozsalam", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CILIUM-001-002/", "source_url": "https://github.com/cilium/cilium/pull/44772", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "repo": "containerd/containerd", "number": 12889, "url": "https://github.com/containerd/containerd/pull/12889", "title": "docker fetcher: strip sensitive headers on descriptor URLs", "category": "fix", "why": "prevents registry-scoped Authorization, Proxy-Authorization, Cookie, and Cookie2 headers from being forwarded to cross-origin descriptor URLs while preserving same-origin registry behavior. public PR #12889 merged into main on 2026-08-25 as commit d7bebd8.", "finding_id": "F-CONTAINERD-DESCURLS-001", "submitted": "2026-02-12", "status": "merged", "classification": { "area": "authorization", "reason": "Descriptor URLs can receive sensitive headers intended for a different destination.", "source": "https://github.com/containerd/containerd/pull/12889", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/containerd/containerd/pull/12889", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "pr", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CONTAINERD-DESCURLS-001/", "source_url": "https://github.com/containerd/containerd/pull/12889", "disclosed": null, "cwe": null, "layer": "authorization" } ], "credited_prs": [ { "repo": "open-policy-agent/gatekeeper", "number": 4351, "url": "https://github.com/open-policy-agent/gatekeeper/pull/4351", "finding_id": "F-GK-EXT-001", "title": "fix: enforce timeout on external data provider requests", "status": "merged", "credit": "thanks @1seal for raising the issue", "classification": { "area": "availability", "reason": "An external operation lacks an effective timeout.", "source": "https://github.com/open-policy-agent/gatekeeper/pull/4351", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GK-EXT-001/", "source_url": "https://github.com/open-policy-agent/gatekeeper/pull/4351", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "openssl/openssl", "number": 30001, "url": "https://github.com/openssl/openssl/pull/30001", "finding_id": "F-OPENSSL-SRTPKDF-002", "title": "srtpkdf input bounds checking", "status": "applied upstream", "credit": "reported by https://github.com/1seal (merged from #30001)", "classification": { "area": "memory-safety", "reason": "SRTP KDF buffer use lacks required input-length validation.", "source": "https://github.com/openssl/openssl/pull/30001", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-SRTPKDF-002/", "source_url": "https://github.com/openssl/openssl/pull/30001", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "repo": "sigstore/sigstore-go", "number": 590, "url": "https://github.com/sigstore/sigstore-go/pull/590", "finding_id": "F-SIG-GO-THRESHOLD-001", "title": "hardening: minimum threshold for withintegratedtimestamps", "status": "merged", "credit": "thanks @1seal for reporting this improvement", "classification": { "area": "integrity", "reason": "Timestamp verification does not enforce the minimum integrated-time threshold.", "source": "https://github.com/sigstore/sigstore-go/pull/590", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIG-GO-THRESHOLD-001/", "source_url": "https://github.com/sigstore/sigstore-go/pull/590", "disclosed": null, "cwe": null, "layer": "integrity" }, { "repo": "letsencrypt/boulder", "number": 8641, "url": "https://github.com/letsencrypt/boulder/pull/8641", "finding_id": "F-BOULDER-009", "title": "Don't modify http.DefaultTransport", "status": "merged", "credit": "thanks to Oleh Konko (@1seal) for reporting this issue (comment by @aarongable).", "classification": { "area": "identity", "reason": "Cloning the HTTP transport confines InsecureSkipVerify and other TLS options to the observer client instead of mutating global defaults. This is identity-verification configuration hardening, not proof of a reachable exploit.", "source": "https://github.com/letsencrypt/boulder/pull/8641", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BOULDER-009/", "source_url": "https://github.com/letsencrypt/boulder/pull/8641", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "theopolis/uefi-firmware-parser", "number": 145, "url": "https://github.com/theopolis/uefi-firmware-parser/pull/145", "finding_ids": [ "F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003", "F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002" ], "title": "Apply hardening fixes from upstream Tiano implementation", "status": "merged", "credit": "PR body: \"Thank you @1seal for mentioning this!\"", "note": "PR #145 includes both ReadCLen and MakeTable bounds checks. Public mapping rechecked 2026-09-25: GHSA-hm2w-vr2p-hq7w / CVE-2026-54334 (ReadCLen) and GHSA-2689-5p89-6j3j / CVE-2026-54333 (MakeTable). One shared fix record, not two additional findings.", "cve": "CVE-2026-54334 / CVE-2026-54333", "classification": { "area": "memory-safety", "reason": "Tiano ReadCLen and MakeTable write outside their intended buffers.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003/", "source_url": "https://github.com/theopolis/uefi-firmware-parser/pull/145", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "repo": "sigstore/rekor", "number": 2755, "url": "https://github.com/sigstore/rekor/pull/2755", "finding_id": "F-REKOR-VERIFY-002", "title": "Type assert the entry bundle when verifying inclusion proof", "status": "merged", "credit": "PR body: \"Thanks to @1seal for reporting this.\"", "classification": { "area": "availability", "reason": "The checked string assertion returns an error for a non-string entry body instead of panicking, protecting verification availability.", "source": "https://github.com/sigstore/rekor/pull/2755", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-REKOR-VERIFY-002/", "source_url": "https://github.com/sigstore/rekor/pull/2755", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "spiffe/spire", "url": "https://github.com/spiffe/spire/releases/tag/v1.14.2", "finding_id": "F-SPIRE-HTTPCHALLENGE-001", "title": "http_challenge SSRF fixed in v1.14.2 and v1.13.4", "status": "released", "credit": "Thank you, Oleh Konko (@1seal) for reporting this issue. also credited in v1.13.4 and CHANGELOG.md.", "classification": { "area": "authorization", "reason": "HTTP challenge handling reaches an untrusted request destination.", "source": "https://github.com/spiffe/spire/releases/tag/v1.14.2", "reviewed": "2026-09-24" }, "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SPIRE-HTTPCHALLENGE-001/", "source_url": "https://github.com/spiffe/spire/releases/tag/v1.14.2", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "containerd/containerd", "number": 13189, "url": "https://github.com/containerd/containerd/pull/13189", "title": "[release/2.1] update to Go 1.25.9, 1.26.2", "finding_id": "F-GO-X509-WILDCARD-CASE-001", "status": "merged", "credit": "PR body includes @1seal in the upstream Go security credit text for Go 1.25.9 / 1.26.2.", "note": "merged into release/2.1 on 2026-04-08; merge commit e4244c720f20.", "classification": { "area": "identity", "reason": "Wildcard case handling bypasses certificate name constraints; downstream receipts share this ID.", "source": "https://github.com/containerd/containerd/pull/13189", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-X509-WILDCARD-CASE-001/", "source_url": "https://github.com/containerd/containerd/pull/13189", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "containerd/containerd", "number": 13190, "url": "https://github.com/containerd/containerd/pull/13190", "title": "[release/2.2] update to Go 1.25.9, 1.26.2", "finding_id": "F-GO-X509-WILDCARD-CASE-001", "status": "merged", "credit": "PR body includes @1seal in the upstream Go security credit text for Go 1.25.9 / 1.26.2.", "note": "merged into release/2.2 on 2026-04-09; merge commit 17847ac84599.", "classification": { "area": "identity", "reason": "Wildcard case handling bypasses certificate name constraints; downstream receipts share this ID.", "source": "https://github.com/containerd/containerd/pull/13189", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-X509-WILDCARD-CASE-001/", "source_url": "https://github.com/containerd/containerd/pull/13190", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "helm/helm", "url": "https://github.com/helm/helm/releases/tag/v4.1.4", "finding_id": "F-HELM-UNTAR-ROOT-COLLAPSE-001", "title": "Helm Chart extraction output directory collapse via Chart.yaml name dot-segment", "status": "released", "credit": "v4.1.4 release note thanks @1seal among the reporters.", "note": "GHSA-hr2v-4r36-88hr / CVE-2026-35206 published; fixed in Helm v4.1.4. changelog lists commit 4e7994d44671 for the chart dot-name path bug.", "classification": { "area": "authorization", "reason": "Archive root handling defeats extraction containment.", "source": "https://github.com/helm/helm/releases/tag/v4.1.4", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-HELM-UNTAR-ROOT-COLLAPSE-001/", "source_url": "https://github.com/helm/helm/releases/tag/v4.1.4", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "testcontainers/testcontainers-go", "number": 3647, "url": "https://github.com/testcontainers/testcontainers-go/pull/3647", "title": "chore: update to Go 1.25.9, 1.26.9", "finding_id": "F-GO-X509-WILDCARD-CASE-001", "status": "merged", "credit": "PR body includes @1seal in the upstream Go security credit text for Go 1.25.9 / 1.26.2.", "note": "merged into main on 2026-04-09; merge commit 580abf68d440. PR title says 1.26.9, body references Go 1.26.2.", "classification": { "area": "identity", "reason": "This downstream Go update includes the wildcard DNS-constraint fix linked to this finding; it is adoption, not a new defect or authored fix.", "source": "https://github.com/testcontainers/testcontainers-go/pull/3647", "reviewed": "2026-09-21" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-X509-WILDCARD-CASE-001/", "source_url": "https://github.com/testcontainers/testcontainers-go/pull/3647", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "google/go-containerregistry", "number": 2255, "url": "https://github.com/google/go-containerregistry/pull/2255", "title": "update to Go 1.26.2", "finding_id": "F-GO-X509-WILDCARD-CASE-001", "status": "merged", "credit": "PR body includes @1seal in the upstream Go security credit text for Go 1.26.2.", "note": "merged into main on 2026-04-11; merge commit f8be1d442e6f.", "classification": { "area": "identity", "reason": "This downstream Go update includes the wildcard DNS-constraint fix linked to this finding; it is adoption, not a new defect or authored fix.", "source": "https://github.com/google/go-containerregistry/pull/2255", "reviewed": "2026-09-21" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-X509-WILDCARD-CASE-001/", "source_url": "https://github.com/google/go-containerregistry/pull/2255", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "rustls/webpki", "number": 469, "url": "https://github.com/rustls/webpki/pull/469", "finding_id": "F-RUSTLS-WEBPKI-001", "title": "Rewrite constraint matching to avoid permissive catch-all branch", "status": "merged", "credit": "PR description says it addresses an issue privately reported by @1seal.", "note": "merged into main on 2026-04-13; merge commit 9e1f4822932b. GHSA-pwjx-qhcg-rvj4 already published for the same finding.", "classification": { "area": "identity", "reason": "CRL authority matching is incomplete.", "source": "https://github.com/rustls/webpki/pull/469", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-RUSTLS-WEBPKI-001/", "source_url": "https://github.com/rustls/webpki/pull/469", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "wolfSSL/wolfssl", "number": 9991, "url": "https://github.com/wolfSSL/wolfssl/pull/9991", "finding_id": "F-WOLFSSL-NC-WILDCARD-001", "title": "Disallow wildcard partial domains when using MatchDomainName.", "status": "merged", "credit": "PR body says: Thanks to Oleh Konko for the report.", "note": "merged into master on 2026-03-19; merge commit 679366a5a49f. v5.9.1-stable release note also credits @1seal for the report.", "classification": { "area": "identity", "reason": "Wildcard certificate names bypass name-constraint checks.", "source": "https://github.com/wolfSSL/wolfssl/pull/9991", "reviewed": "2026-09-24" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WOLFSSL-NC-WILDCARD-001/", "source_url": "https://github.com/wolfSSL/wolfssl/pull/9991", "disclosed": null, "cwe": null, "layer": "identity" }, { "repo": "mozilla-firefox/firefox", "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020535", "finding_id": "F-FIREFOX-IPC-MLS-009", "title": "MLS IPC principal validation hardening", "status": "released", "credit": "Mozilla Bug 2020535 lists Oleh Konko (1seal) as reporter. Patch author: Benjamin Beurdouche; review: nika. Reporter credit does not imply patch authorship.", "note": "Mozilla records RESOLVED FIXED and firefox152 fixed (Firefox 152). Classified sec-other and unsupported-config; this is a hardening result, not a confirmed HIGH-severity vulnerability or a new CVE. The original harness ran in the same process and does not establish the broader scenario between independent processes. Private attachments are not republished.", "related_sources": [ { "label": "Principal validation patch (Bug 2020535)", "url": "https://github.com/mozilla-firefox/firefox/commit/297025166caa9b96ea2b43363a18c640185e2e2c" } ], "classification": { "area": "identity", "reason": "The public patch validates the incoming MLS principal against the sending content process remote type. Mozilla classifies the report as sec-other and unsupported-config.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020535", "reviewed": "2026-10-07" }, "record_type": "credited", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-FIREFOX-IPC-MLS-009/", "source_url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020535", "disclosed": null, "cwe": null, "layer": "identity" } ], "credited_prs_pending": [ { "finding_id": "F-NPM-CLI-001", "repo": "npm/cli", "url": "https://github.com/npm/bin-links/pull/173", "title": "Global executable ownership check accepts a prefix-colliding package directory", "status": "fixed publicly", "patched": "bin-links 6.0.1; also verified in npm 11.15.0 (bin-links 6.0.2)", "source_reviewed": "2026-09-26", "note": "When a user installs a package globally, bin-links decides whether an existing executable belongs to that package. A startsWith comparison also accepted sibling directories whose names share the same prefix, permitting an unrelated executable link or shim to be replaced without force. PR #173, merged 13 May 2026, requires an exact directory match or a prefix followed by the platform path separator in check-bin, link-gently and shim-bin, with regression tests. The boundary check is present in bin-links 6.0.1 and the bin-links 6.0.2 bundled with npm 11.15.0. This concerns package installation and executable ownership, not execution without a user installing a package. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "A textual path prefix is mistaken for package ownership, allowing replacement of another package's executable link.", "source": "https://github.com/npm/bin-links/pull/173", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "bin-links 6.0.1: directory-boundary check", "url": "https://github.com/npm/bin-links/blob/v6.0.1/lib/check-bin.js" }, { "label": "npm 11.15.0: bundled dependency version", "url": "https://github.com/npm/cli/blob/v11.15.0/node_modules/bin-links/package.json" }, { "label": "npm 11.15.0: executable ownership check", "url": "https://github.com/npm/cli/blob/v11.15.0/node_modules/bin-links/lib/check-bin.js" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NPM-CLI-001/", "source_url": "https://github.com/npm/bin-links/pull/173", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-DOCUSAURUS-DEPLOY-ARGINJECT-001", "repo": "facebook/docusaurus", "url": "https://github.com/facebook/docusaurus/commit/23e6a41db15f17251fe22e93537ebede354e20c0", "title": "Deployment branch text is reinterpreted as Git command arguments", "status": "merged to main/pre-release only", "patched": "main and 4.0.0-canary-6848; stable 3.10.2 still uses the old command path", "source_reviewed": "2026-09-26", "note": "The reported path requires control of the deployment branch supplied to the deploy command. Whitespace in that value could introduce additional Git arguments when the command string was parsed. The 3 September 2026 execa migration replaces commandSync strings with executable-and-argument arrays, keeping the branch value as one argument for clone, checkout and push. The change is present in the published 4.0.0-canary-6848 package; the inspected stable 3.10.2 source still uses commandSync. This records closure of the argument-splitting path, not proof that every possible Git option or deployment configuration is safe. No stable fixed release is claimed. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "semantics", "reason": "Branch-name data is interpolated into a command string instead of remaining one argument.", "source": "https://github.com/facebook/docusaurus/commit/23e6a41db15f17251fe22e93537ebede354e20c0", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "Published canary deploy implementation", "url": "https://unpkg.com/@docusaurus/core@4.0.0-canary-6848/lib/commands/deploy.js" }, { "label": "Stable 3.10.2: old command-string implementation", "url": "https://github.com/facebook/docusaurus/blob/v3.10.2/packages/docusaurus/src/commands/deploy.ts" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-DOCUSAURUS-DEPLOY-ARGINJECT-001/", "source_url": "https://github.com/facebook/docusaurus/commit/23e6a41db15f17251fe22e93537ebede354e20c0", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-PROXYGEN-BINARYHTTP-001", "repo": "facebook/proxygen", "url": "https://github.com/facebook/proxygen/commit/479eb5574195764e80e6cedebef669f6baa85083", "title": "Binary HTTP field-section length includes its own prefix", "status": "fixed on main (release not confirmed)", "patched": "main fix commit; v2026.09.21.00 still contains the old parser", "source_reviewed": "2026-09-26", "note": "A crafted Binary HTTP message can exercise the known-length header parser, where the bytes used to encode the section length were included in the section byte count. The 21 September 2026 change starts a separate fieldSectionParsed counter at zero, bounds the field-section cursor and rejects excess consumption. This closes the recorded framing error in HTTPBinaryCodec. The inspected v2026.09.21.00 release was produced before that change and retains the old implementation. The public evidence supports a parser-boundary fix on main, not confirmed request smuggling through a particular deployed proxy chain or a fixed stable release. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "integrity", "reason": "Incorrect length accounting shifts the boundary between a Binary HTTP header section and the following data.", "source": "https://github.com/facebook/proxygen/commit/479eb5574195764e80e6cedebef669f6baa85083", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "Release v2026.09.21.00: parser before the fix", "url": "https://github.com/facebook/proxygen/blob/v2026.09.21.00/proxygen/lib/http/codec/HTTPBinaryCodec.cpp" }, { "label": "Release v2026.09.21.00", "url": "https://github.com/facebook/proxygen/releases/tag/v2026.09.21.00" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROXYGEN-BINARYHTTP-001/", "source_url": "https://github.com/facebook/proxygen/commit/479eb5574195764e80e6cedebef669f6baa85083", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-WHATSAPP-WARAFT-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "WhatsApp/waraft", "url": "https://github.com/WhatsApp/waraft/commit/32ae20329488d110b4303ef8ca1022ce02c43fe4", "title": "Snapshot transport accepts file paths outside its destination root", "status": "fixed on main (release not confirmed)", "patched": "public source commit; a separate fixed release is not established", "source_reviewed": "2026-09-26", "note": "Snapshot transport metadata from a connected Erlang peer supplies relative file paths that were joined to the receiving root without a confinement check. The 22 July 2026 patch validates every path with filelib:safe_relative_path/2 before creating transport state and rejects the whole transport if a path is unsafe. This covers parent traversal, absolute paths and symlink escapes handled by that check. The commit refers to an external security report, but does not by itself identify this finding's reporter. A fixed release and production rollout were not established. This is the waraft library and its peer trust boundary, not an unauthenticated attack on WhatsApp Messenger. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "A peer-supplied snapshot path crosses the receiving transport's filesystem boundary.", "source": "https://github.com/WhatsApp/waraft/commit/32ae20329488d110b4303ef8ca1022ce02c43fe4", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "Patched snapshot transport implementation", "url": "https://github.com/WhatsApp/waraft/blob/32ae20329488d110b4303ef8ca1022ce02c43fe4/src/wa_raft_transport.erl" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WHATSAPP-WARAFT-001/", "source_url": "https://github.com/WhatsApp/waraft/commit/32ae20329488d110b4303ef8ca1022ce02c43fe4", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-PROTON-VPN-ANDROID-GLANCE-001", "repo": "ProtonVPN/android-app", "url": "https://github.com/ProtonVPN/android-app/commit/114faaaf270647f01e1614731b93241c07366f98", "title": "Exported activity accepts actions intended for internal VPN widgets", "status": "fixed publicly", "patched": "5.19.72.0 source and release; installed store binaries not reverified", "source_reviewed": "2026-09-26", "note": "A local Android application could address the exported activity with intent data intended for the VPN widget action path. The 16 July 2026 patch introduces the non-exported InternalMainActivity alias and makes processInternalIntent honor glance_action only when the addressed component is that internal alias. The manifest and handler are present in public release 5.19.72.0. This establishes the source-level separation of external and internal actions; it does not establish a remote network attack, secret recovery, or that every installed store build has been updated. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "Externally supplied activity intents can enter a path intended only for internal widget actions.", "source": "https://github.com/ProtonVPN/android-app/commit/114faaaf270647f01e1614731b93241c07366f98", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "5.19.72.0: internal action gate", "url": "https://github.com/ProtonVPN/android-app/blob/5.19.72.0/app/src/main/java/com/protonvpn/android/redesign/app/ui/MainActivity.kt" }, { "label": "5.19.72.0: non-exported alias", "url": "https://github.com/ProtonVPN/android-app/blob/5.19.72.0/app/src/main/AndroidManifest.xml" }, { "label": "5.19.72.0 release", "url": "https://github.com/ProtonVPN/android-app/releases/tag/5.19.72.0" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-VPN-ANDROID-GLANCE-001/", "source_url": "https://github.com/ProtonVPN/android-app/commit/114faaaf270647f01e1614731b93241c07366f98", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-PROTON-IOS-AUTH-001", "repo": "protonpass/ios-authenticator", "url": "https://github.com/protonpass/ios-authenticator/commit/2dfa196a08011687ca596cbd96a1bf1729ff1251", "title": "Authenticator processes OTP deep links before completing local authentication", "status": "fixed publicly", "patched": "1.4.0 source tag; App Store delivery not independently verified", "source_reviewed": "2026-09-26", "note": "Opening an otpauth deep link while the application is locked could enter the import path before authentication. The 17 April 2026 patch defers the URL in pendingDeepLink while showEntries is false and processes it only after authenticated entries may be shown. The same gate is present in tag 1.4.0. The confirmed change is the ordering of local authentication and deep-link handling. It is not evidence of secret extraction, nor an independent runtime demonstration that the locked vault was modified. Presence in a source tag does not establish the delivery date or contents of an App Store binary. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "An incoming OTP URL reaches import processing before the local authentication gate is satisfied.", "source": "https://github.com/protonpass/ios-authenticator/commit/2dfa196a08011687ca596cbd96a1bf1729ff1251", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "1.4.0: authentication gate and pending deep link", "url": "https://github.com/protonpass/ios-authenticator/blob/1.4.0/Authenticator/App/AuthenticatorApp.swift" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-IOS-AUTH-001/", "source_url": "https://github.com/protonpass/ios-authenticator/commit/2dfa196a08011687ca596cbd96a1bf1729ff1251", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-PROTON-DRIVE-DEEPLINK-001", "repo": "ProtonDriveApps/android-drive", "url": "https://github.com/ProtonDriveApps/android-drive/commit/74b5c034d1070fdcc378027dd4e1e2cdcd818fb8", "title": "Deep-link upload path omits external URI validation", "status": "fixed publicly", "patched": "2.40.0 source tag; also present in the later 3.0.0 source release", "source_reviewed": "2026-09-26", "note": "Upload parameters received through navigation/deep-link state were accepted without applying the existing external URI guard. The 20 July 2026 update injects ValidateExternalUri into UploadToViewModel and validates every incoming URI before constructing UploadParameters. The guard rejects disallowed file URIs, including app-private paths, rather than treating incoming navigation data as trusted. The check is present in tag 2.40.0 and the later public 3.0.0 source release. The reported flow still requires the upload interaction; this entry does not claim silent exfiltration to an attacker account or verified rollout to installed Android binaries. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "A second upload entry point bypasses URI validation already used for external inputs.", "source": "https://github.com/ProtonDriveApps/android-drive/commit/74b5c034d1070fdcc378027dd4e1e2cdcd818fb8", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "2.40.0: upload entry-point validation", "url": "https://github.com/ProtonDriveApps/android-drive/blob/2.40.0/app/src/main/kotlin/me/proton/android/drive/ui/viewmodel/UploadToViewModel.kt" }, { "label": "2.40.0: external URI policy", "url": "https://github.com/ProtonDriveApps/android-drive/blob/2.40.0/app/src/main/kotlin/me/proton/android/drive/usecase/ValidateExternalUri.kt" }, { "label": "3.0.0 source release", "url": "https://github.com/ProtonDriveApps/android-drive/releases/tag/3.0.0" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-DRIVE-DEEPLINK-001/", "source_url": "https://github.com/ProtonDriveApps/android-drive/commit/74b5c034d1070fdcc378027dd4e1e2cdcd818fb8", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-PROTON-WALLET-FLUTTER-001", "repo": "ProtonWallet/flutter-app", "url": "https://github.com/ProtonWallet/flutter-app/commit/e40a7e56c0ab0f3e36d057282da5342097d67040", "title": "Recovery and wallet import logging includes mnemonic words", "status": "fixed publicly", "patched": "v1.3.0+115 source tag; store rollout not independently verified", "source_reviewed": "2026-09-26", "note": "Recovery activation and reactivation logged the generated mnemonic words; the import path also logged mnemonic content. The 16 July 2026 patch replaces recovery log values with a fixed message and changes import logging to a word count rather than the words. The change is present in tag v1.3.0+115. Exposure depends on the relevant logging path being active and someone gaining access to its output. The fix removes these disclosures from future log events; it does not erase old logs, establish compromise of every wallet, or prove that a particular store-distributed binary has been updated. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "confidentiality", "reason": "Mnemonic material is copied from recovery/import processing into diagnostic logs.", "source": "https://github.com/ProtonWallet/flutter-app/commit/e40a7e56c0ab0f3e36d057282da5342097d67040", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "v1.3.0+115: recovery logging without words", "url": "https://github.com/ProtonWallet/flutter-app/blob/v1.3.0%2B115/rust/src/proton_wallet/features/proton_recovery.rs" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-WALLET-FLUTTER-001/", "source_url": "https://github.com/ProtonWallet/flutter-app/commit/e40a7e56c0ab0f3e36d057282da5342097d67040", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-BC-NC-MULTIAT-001", "repo": "bcgit/bc-java", "url": "https://github.com/bcgit/bc-java/commit/a535c77060258d8ad5cd2aaadd723894aee3b695", "title": "Ambiguous multi-at-sign mailbox evades excluded email name constraints", "status": "fixed publicly", "patched": "Java 1.85 and C# 2.7.0, with default strict email-name parsing", "source_reviewed": "2026-09-26", "note": "A certificate email name with an at-sign inside a quoted local part could be split at the first at-sign, causing an excluded-domain check to miss the actual mailbox domain. Java commit a535c770 on 2 July 2026 and C# commit 9c2f6510 on 6 July reject ambiguous multiple-at-sign tested names when email constraints apply; regression tests include the reported quoted-local-part form. Both Java 1.85 and C# 2.7.0 contain the check. The optional lenient-rfc822-name compatibility setting restores the old parsing, so the fixed-version statement assumes the default strict configuration. Bouncy Castle credits 1seal for X.509 rfc822Name name-constraint security analysis and classifies this report as hardening, without a CVE. This is separate from trailing-dot normalization; no severity or fresh end-to-end retest is inferred.", "credit": "1seal (Oleh Konko), acknowledged in Bouncy Castle CONTRIBUTORS.md for rfc822Name name-constraint hardening", "classification": { "area": "identity", "reason": "Splitting a quoted mailbox at the first at-sign compares the wrong domain against certificate name constraints.", "source": "https://github.com/bcgit/bc-java/commit/a535c77060258d8ad5cd2aaadd723894aee3b695", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "C# ambiguity rejection and regression tests", "url": "https://github.com/bcgit/bc-csharp/commit/9c2f651024874331c18a6bd6fd60cd031ebf7759" }, { "label": "Java 1.85: constrained email checks", "url": "https://github.com/bcgit/bc-java/blob/r1rv85/core/src/main/java/org/bouncycastle/asn1/x509/PKIXNameConstraintValidator.java" }, { "label": "C# 2.7.0: strict check and compatibility switch", "url": "https://github.com/bcgit/bc-csharp/blob/release-2.7.0/crypto/src/pkix/PkixNameConstraintValidator.cs" }, { "label": "Bouncy Castle contributor credit", "url": "https://github.com/bcgit/bc-java/blob/main/CONTRIBUTORS.md" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BC-NC-MULTIAT-001/", "source_url": "https://github.com/bcgit/bc-java/commit/a535c77060258d8ad5cd2aaadd723894aee3b695", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-WHISPER-001-002", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-02" }, "repo": "ggml-org/whisper.cpp", "url": "https://github.com/ggml-org/whisper.cpp/commit/df1547b6fe362556e48fd21f386c6eee85b971fe", "title": "Model tensor dimension count can exceed a four-element stack array", "status": "fixed publicly", "patched": "verified in v1.9.4; not asserted to be the first fixed version", "source_reviewed": "2026-09-26", "note": "Loading a crafted model file could provide an out-of-range tensor dimension count before values were read into ne[4]. The 7 August 2026 patch rejects n_dims below zero or above four before the dimension loop in both whisper_model_load and whisper_vad_init_with_params; the commit also hardens the Parakeet path. Both reported loader checks are present in stable v1.9.4. This requires loading an untrusted model, not merely transcribing an audio sample. The patch supports closure of the dimension-count stack-write path, not a demonstrated code-execution chain or closure of the distinct F-WHISPER-001-001 report. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "memory-safety", "reason": "A model-controlled dimension count indexes beyond the fixed-size dimension array in the model loaders.", "source": "https://github.com/ggml-org/whisper.cpp/commit/df1547b6fe362556e48fd21f386c6eee85b971fe", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "v1.9.4: both model-loader dimension checks", "url": "https://github.com/ggml-org/whisper.cpp/blob/v1.9.4/src/whisper.cpp" }, { "label": "v1.9.4 release", "url": "https://github.com/ggml-org/whisper.cpp/releases/tag/v1.9.4" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WHISPER-001-002/", "source_url": "https://github.com/ggml-org/whisper.cpp/commit/df1547b6fe362556e48fd21f386c6eee85b971fe", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-NEO-NOTARY-001", "repo": "neo-project/neo", "url": "https://github.com/neo-project/neo/commit/abbc3a259e93459e7b4b9174b62a3189410fbd44", "title": "Notary-sponsored transaction fees are not bounded by the individual payer deposit", "status": "fixed publicly", "patched": "v3.10.1; network deployment not independently verified", "source_reviewed": "2026-09-26", "note": "Notary-assisted transaction validation must account for each depositor's balance and fees already reserved by pending transactions. The 3 July 2026 patch introduces primary/secondary payer tracking, uses the individual Notary.BalanceOf value for sponsored transactions, accumulates mempool fees against that payer and rejects missing or negative balances during persistence. Regression coverage accompanies the accounting change. These changes are included in release v3.10.1. The evidence supports a released deposit/fee-accounting fix, not confirmation that every network node upgraded, that funds were stolen or recovered, or that a particular deployed chain reproduced the reported effect. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "integrity", "reason": "Fee accounting uses a shared payer boundary instead of the individual notary depositor and accumulated obligations.", "source": "https://github.com/neo-project/neo/commit/abbc3a259e93459e7b4b9174b62a3189410fbd44", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "v3.10.1: payer-specific pending-fee accounting", "url": "https://github.com/neo-project/neo/blob/v3.10.1/src/Neo/Ledger/TransactionVerificationContext.cs" }, { "label": "v3.10.1: notary persistence checks", "url": "https://github.com/neo-project/neo/blob/v3.10.1/src/Neo/SmartContract/Native/Notary.cs" }, { "label": "v3.10.1 release", "url": "https://github.com/neo-project/neo/releases/tag/v3.10.1" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NEO-NOTARY-001/", "source_url": "https://github.com/neo-project/neo/commit/abbc3a259e93459e7b4b9174b62a3189410fbd44", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-LIBSIGNAL-MAC-LOG-001", "repo": "signalapp/libsignal", "url": "https://github.com/signalapp/libsignal/commit/0dc09edf868c7fe21a78ced960a621debbd95513", "title": "Failed message verification logs received and computed authentication tags", "status": "fixed publicly", "patched": "v0.103.0 library release; downstream application rollout not established", "source_reviewed": "2026-09-26", "note": "On a failed message MAC comparison, the verifier logged both the received tag and its locally computed counterpart. The 17 September 2026 commit removes that diagnostic output while retaining constant-time comparison and verification failure. The change is present in the v0.103.0 library release. The reported observation requires a failed verification and access to the logs. MAC tags are not encryption keys: removing their log output does not by itself prove prior key recovery, a break of end-to-end encryption, or remote access to logs. Adoption by Signal clients was not independently established in this check. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "confidentiality", "reason": "Authentication-tag values from message verification are unnecessarily exposed through a diagnostic log.", "source": "https://github.com/signalapp/libsignal/commit/0dc09edf868c7fe21a78ced960a621debbd95513", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "v0.103.0: message authentication verification", "url": "https://github.com/signalapp/libsignal/blob/v0.103.0/rust/protocol/src/protocol.rs" }, { "label": "v0.103.0 release", "url": "https://github.com/signalapp/libsignal/releases/tag/v0.103.0" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LIBSIGNAL-MAC-LOG-001/", "source_url": "https://github.com/signalapp/libsignal/commit/0dc09edf868c7fe21a78ced960a621debbd95513", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-WIREGUARD-001-001", "repo": "WireGuard/wireguard-windows", "url": "https://github.com/WireGuard/wireguard-windows/commit/b1b1bfee5dd393332976f2f200151838a3e242ef", "title": "Configuration loader builds a path before validating the tunnel name", "status": "fixed publicly", "patched": "v1.1; recorded as defensive validation, not a confirmed reachable exploit", "source_reviewed": "2026-09-26", "note": "LoadFromName constructed a configuration path from a supplied tunnel name without first calling TunnelNameIsValid. The 3 May 2026 patch adds that validation before path construction and rejects invalid names. The guard is present in v1.1 and absent from the inspected v1.0.1 source. The maintainer describes the path as not really reachable and the change as a missing defensive check. This record therefore documents matching source hardening, not acceptance of a HIGH-severity vulnerability, a confirmed unprivileged attack path, or attribution of the patch to this report. Public-source review does not establish vendor attribution, an assigned severity or a fresh end-to-end retest.", "classification": { "area": "authorization", "reason": "A tunnel-name-to-path conversion lacks a local name-validation boundary; the upstream fix adds it defensively.", "source": "https://github.com/WireGuard/wireguard-windows/commit/b1b1bfee5dd393332976f2f200151838a3e242ef", "reviewed": "2026-09-26" }, "related_sources": [ { "label": "v1.1: validated configuration loading", "url": "https://github.com/WireGuard/wireguard-windows/blob/v1.1/conf/store.go" }, { "label": "v1.0.1: earlier loader", "url": "https://github.com/WireGuard/wireguard-windows/blob/v1.0.1/conf/store.go" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WIREGUARD-001-001/", "source_url": "https://github.com/WireGuard/wireguard-windows/commit/b1b1bfee5dd393332976f2f200151838a3e242ef", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-LEDGER-BTC-PREIMAGE-001", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/7f8e57be74052a9b31c240d9a9e7b56a6f655aee", "title": "bound preimage writes by the output buffer capacity", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-03-27", "note": "call_get_preimage now rejects an oversized preimage and checks buffer writes. The finding-to-patch mapping is based on the reported callsite and public diff, not public attribution of this finding ID. A fixed release and device rollout were not independently checked.", "classification": { "area": "memory-safety", "reason": "The patch bounds writes to a caller-provided preimage buffer.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/7f8e57be74052a9b31c240d9a9e7b56a6f655aee", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-PREIMAGE-001/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/7f8e57be74052a9b31c240d9a9e7b56a6f655aee", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-BTC-BIP32-001", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/0586ab2f940c290dcaba89ca307b85589831aa2e", "title": "correct an off-by-one move in BIP32 derivation parsing", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-10", "note": "extract_bip32_derivation changes the memmove length from out_data_length - d + 1 to out_data_length - d. This is a different callsite from F-LEDGER-BTC-MERKLE-001, but both mappings share the same upstream commit; they are not two independent patch artifacts. Mapping is based on source comparison. Release inclusion and device rollout were not independently checked.", "classification": { "area": "memory-safety", "reason": "The corrected move length prevents copying one byte beyond the intended buffer span.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/0586ab2f940c290dcaba89ca307b85589831aa2e", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-BIP32-001/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/0586ab2f940c290dcaba89ca307b85589831aa2e", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-BTC-USTREAM-001", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/8ff2b62094af27f41d46b84ff2f49e94d8b43dc2", "title": "reject empty chunks in streamed preimage handling", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-27", "note": "stream_preimage now rejects partial_data_len == 0. The patch matches the reported empty-chunk path. Mapping is by source comparison, without a claim of public vendor attribution or independently verified release rollout.", "classification": { "area": "availability", "reason": "The parser rejects an empty streamed chunk instead of proceeding through the malformed-input path.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/8ff2b62094af27f41d46b84ff2f49e94d8b43dc2", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-USTREAM-001/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/8ff2b62094af27f41d46b84ff2f49e94d8b43dc2", "cwe": null, "layer": "availability" }, { "finding_id": "F-LEDGER-BTC-OBO-001", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/e04898b32a7eed5c4fa2d4611181113b63ae9644", "title": "reject a derivation step at the array capacity boundary", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-18", "note": "wallet parsing changes the derivation-length check from > to >= before writing a step. The reported boundary condition matches this public diff. Release inclusion and device rollout were not independently checked; public credit is not asserted.", "classification": { "area": "memory-safety", "reason": "The corrected comparison prevents an array write when the derivation buffer is already full.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/e04898b32a7eed5c4fa2d4611181113b63ae9644", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-OBO-001/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/e04898b32a7eed5c4fa2d4611181113b63ae9644", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-BTC-NEGRC-002", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/70dcdf0cac8be7a35468a0c83fe0e5cbedcecbc6", "title": "reject all negative merkleized-map return values before using their length", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-27", "note": "txhashes and sign_psbt callers check < 0 rather than only == -1, preventing other error returns from being used as lengths. Mapping is based on the reported callsites and public diff. Release inclusion and device rollout were not independently checked.", "classification": { "area": "memory-safety", "reason": "Negative error codes must not cross into unsigned buffer-length operations.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/70dcdf0cac8be7a35468a0c83fe0e5cbedcecbc6", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-NEGRC-002/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/70dcdf0cac8be7a35468a0c83fe0e5cbedcecbc6", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-BTC-MUSIG-001", "repo": "LedgerHQ/app-bitcoin", "url": "https://github.com/LedgerHQ/app-bitcoin/commit/78bac7790772b6f0adefecc76be4c4d514ce5fa7", "title": "clear MuSig nonce-related buffers on error paths", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-27", "note": "nonce-related stack buffers are cleared through a shared cleanup path, including errors. This source-level mapping is limited to secret-buffer cleanup, not all MuSig security properties. Release inclusion and device rollout were not independently checked.", "classification": { "area": "confidentiality", "reason": "Nonce-derived secret material is cleared before returning from the signing operation.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/78bac7790772b6f0adefecc76be4c4d514ce5fa7", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-BTC-MUSIG-001/", "source_url": "https://github.com/LedgerHQ/app-bitcoin/commit/78bac7790772b6f0adefecc76be4c4d514ce5fa7", "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-LEDGER-ETH-GCS-COLLECTION-OOBWRITE-001", "repo": "LedgerHQ/app-ethereum", "url": "https://github.com/LedgerHQ/app-ethereum/commit/2fb636d904f4528eaa4f84ef89f05179f0b4999c", "title": "enforce the collection capacity before adding a data-path element", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-03-06", "note": "the collection capacity check changes from > MAX to >= MAX before the write. The public commit is dated March 6; this is not a claimed release date. Mapping is based on the reported callsite, not a vendor severity assessment or public finding-ID attribution.", "classification": { "area": "memory-safety", "reason": "The data-path collection must reject an element before an out-of-bounds array write.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/2fb636d904f4528eaa4f84ef89f05179f0b4999c", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-ETH-GCS-COLLECTION-OOBWRITE-001/", "source_url": "https://github.com/LedgerHQ/app-ethereum/commit/2fb636d904f4528eaa4f84ef89f05179f0b4999c", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-ETH-USTREAM-001", "repo": "LedgerHQ/app-ethereum", "url": "https://github.com/LedgerHQ/app-ethereum/commit/48f77149ad40d5b81777466de9becb3dc241152f", "title": "preserve chunk offsets while parsing RLP chain ID and nonce", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-13", "note": "chain ID and nonce copy destinations now include currentFieldPos. The report and patch have the same calendar date; their ordering and a causal link are not established. This is a source-level match, not a claim of vendor credit or verified device rollout.", "classification": { "area": "integrity", "reason": "Chunked input must retain the same parsed transaction fields as contiguous input.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/48f77149ad40d5b81777466de9becb3dc241152f", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-ETH-USTREAM-001/", "source_url": "https://github.com/LedgerHQ/app-ethereum/commit/48f77149ad40d5b81777466de9becb3dc241152f", "cwe": null, "layer": "integrity" }, { "finding_id": "F-LEDGER-ETH-GCS-U16-OFFSET-SPLICE-001", "repo": "LedgerHQ/app-ethereum", "url": "https://github.com/LedgerHQ/app-ethereum/commit/2a96dc8d0b3a7111ef38cdb0a1365da46fae5a07", "title": "reject truncated calldata sizes and offsets in generic clear signing", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-08-25", "note": "path_ref, path_leaf and path_array reject nonzero high bytes before reading a 16-bit size or offset. This matches the reported truncation vector; it does not establish fixes for other plugin or nested-offset reports. Public credit, a fixed release and device rollout are not asserted.", "classification": { "area": "semantics", "reason": "Truncating a calldata offset can make the displayed field differ from the field selected by the full encoded offset.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/2a96dc8d0b3a7111ef38cdb0a1365da46fae5a07", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-ETH-GCS-U16-OFFSET-SPLICE-001/", "source_url": "https://github.com/LedgerHQ/app-ethereum/commit/2a96dc8d0b3a7111ef38cdb0a1365da46fae5a07", "cwe": null, "layer": "semantics" }, { "finding_id": "F-VAULT-ACME-EAB-PANIC-001", "repo": "hashicorp/vault", "url": "https://github.com/hashicorp/vault/commit/daa03407c0d8042105f8af4df0a6c5e056482db0", "title": "reject malformed ACME external-account-binding protected fields without a panic", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-16", "note": "verifyEabPayload replaces an unchecked string assertion with a type check and tests object, array, number and boolean inputs. This is separate from the ACME validation SSRF record. The reported callsite matches the patch; a fixed release was not independently checked.", "classification": { "area": "availability", "reason": "Malformed JSON types can cause a panic before the external-account-binding payload is rejected.", "source": "https://github.com/hashicorp/vault/commit/daa03407c0d8042105f8af4df0a6c5e056482db0", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-VAULT-ACME-EAB-PANIC-001/", "source_url": "https://github.com/hashicorp/vault/commit/daa03407c0d8042105f8af4df0a6c5e056482db0", "cwe": null, "layer": "availability" }, { "finding_id": "F-NITRO-CMS-001", "repo": "aws/aws-nitro-enclaves-sdk-c", "url": "https://github.com/aws/aws-nitro-enclaves-sdk-c/commit/b5ea92c368d565191c09ffff41275b6dc769ccb6", "title": "avoid ciphertext-sized stack allocation in CMS decryption", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-02-13", "note": "aws_cms_cipher_decrypt replaces a variable-length stack array with heap allocation, error handling and cleanup. This matches the reported stack-exhaustion path, not the separate IV-length finding. Release inclusion and deployed consumers were not independently checked.", "classification": { "area": "availability", "reason": "A ciphertext-sized stack allocation can exhaust the stack during decryption.", "source": "https://github.com/aws/aws-nitro-enclaves-sdk-c/commit/b5ea92c368d565191c09ffff41275b6dc769ccb6", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NITRO-CMS-001/", "source_url": "https://github.com/aws/aws-nitro-enclaves-sdk-c/commit/b5ea92c368d565191c09ffff41275b6dc769ccb6", "cwe": null, "layer": "availability" }, { "finding_id": "F-AWS-CLI-BOTOCORE-S3SSRF-001", "repo": "boto/botocore", "url": "https://github.com/boto/botocore/commit/86d458dd4b8aeeb02a5ab198194b4e61569663ce", "title": "validate the region name supplied by an S3 redirect", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-03-04", "note": "PR #3644 validates region names from S3 redirect headers, response bodies and the HEAD fallback before endpoint use. Mapping is based on the reported redirect path and public diff. This does not establish a CVE assignment or a fixed AWS CLI release.", "classification": { "area": "authorization", "reason": "A server-provided region must not redirect credential-bearing client requests outside the intended endpoint boundary.", "source": "https://github.com/boto/botocore/commit/86d458dd4b8aeeb02a5ab198194b4e61569663ce", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-CLI-BOTOCORE-S3SSRF-001/", "source_url": "https://github.com/boto/botocore/commit/86d458dd4b8aeeb02a5ab198194b4e61569663ce", "cwe": null, "layer": "authorization" }, { "finding_id": "F-TUF-002", "repo": "theupdateframework/go-tuf", "url": "https://github.com/theupdateframework/go-tuf/commit/f400bf4c20476804475d34239f01212e1041ec38", "title": "create TUF cache directories with restrictive permissions", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-01-21", "note": "PR #714 creates cache directories with mode 0700 instead of os.ModePerm. The change does not repair permissions on already-existing directories. This is the go-tuf cache-permission finding, not python-tuf bootstrap PR #2903. Release inclusion was not independently checked.", "classification": { "area": "authorization", "reason": "Restrictive creation permissions prevent other local users from modifying newly created cache directories.", "source": "https://github.com/theupdateframework/go-tuf/commit/f400bf4c20476804475d34239f01212e1041ec38", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TUF-002/", "source_url": "https://github.com/theupdateframework/go-tuf/commit/f400bf4c20476804475d34239f01212e1041ec38", "cwe": null, "layer": "authorization" }, { "finding_id": "F-ARGOPROJ-001", "repo": "argoproj/argo-workflows", "url": "https://github.com/argoproj/argo-workflows/commit/7dc19c8a3306a5085ae92ceab56726933fb1aa9e", "title": "limit webhook interceptor request bodies before reading them", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-04-23", "note": "the interceptor reads at most 2 MiB plus one byte, rejects an oversized body and adds a regression test. This matches the reported unbounded-read callsite. No unpublished advisory identifier is exposed here; a fixed release was not independently checked.", "classification": { "area": "availability", "reason": "A webhook request body must be bounded before allocating memory for the entire input.", "source": "https://github.com/argoproj/argo-workflows/commit/7dc19c8a3306a5085ae92ceab56726933fb1aa9e", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ARGOPROJ-001/", "source_url": "https://github.com/argoproj/argo-workflows/commit/7dc19c8a3306a5085ae92ceab56726933fb1aa9e", "cwe": null, "layer": "availability" }, { "finding_id": "F-OTELCOLLECTORCONTRIB-001", "repo": "open-telemetry/opentelemetry-collector-contrib", "url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/commit/d3308cffca3a9dccbafe1ca1b8d7a30420d0948b", "title": "reject grouping file-exporter traversal through Windows path separators", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-06-29", "note": "PR #49195 normalizes Windows backslashes before path containment checks and adds traversal tests. This matches the reported fileexporter path, not the separate Collector snappy issue. Release inclusion and a public advisory assignment were not independently checked.", "classification": { "area": "authorization", "reason": "A grouping value must not select an output file outside the configured directory.", "source": "https://github.com/open-telemetry/opentelemetry-collector-contrib/commit/d3308cffca3a9dccbafe1ca1b8d7a30420d0948b", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OTELCOLLECTORCONTRIB-001/", "source_url": "https://github.com/open-telemetry/opentelemetry-collector-contrib/commit/d3308cffca3a9dccbafe1ca1b8d7a30420d0948b", "cwe": null, "layer": "authorization" }, { "finding_id": "F-HEADSCALE-001-002", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "juanfont/headscale", "url": "https://github.com/juanfont/headscale/commit/42b8c779a02e5bfad6cef5967a7f2e2a107a2707", "title": "bound the verify endpoint request body", "status": "fixed publicly", "disclosed": "2026-04-10", "note": "The /verify handler previously read the request body without a local size cap. Commit 42b8c779 of 10 April 2026 wraps it in http.MaxBytesReader with a 4 KiB limit before io.ReadAll, returns HTTP 413 for oversized input and adds tests. The bounded reader is present in stable v0.29.0, replacing the earlier source-only release caveat. This is distinct from the /machine/map body-limit finding. Matching is by the reported callsite and patch; release availability does not establish vendor credit or deployment to every Headscale server.", "classification": { "area": "availability", "reason": "The request body is capped before an unbounded allocation in the verification handler.", "source": "https://github.com/juanfont/headscale/commit/42b8c779a02e5bfad6cef5967a7f2e2a107a2707", "reviewed": "2026-09-26" }, "patched": "v0.29.0", "source_reviewed": "2026-09-26", "related_sources": [ { "label": "v0.29.0: bounded verify handler", "url": "https://github.com/juanfont/headscale/blob/v0.29.0/hscontrol/handlers.go" }, { "label": "v0.29.0 release", "url": "https://github.com/juanfont/headscale/releases/tag/v0.29.0" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-HEADSCALE-001-002/", "source_url": "https://github.com/juanfont/headscale/commit/42b8c779a02e5bfad6cef5967a7f2e2a107a2707", "cwe": null, "layer": "availability" }, { "finding_id": "F-TGDESKTOP-REFLECTOR-001", "repo": "TelegramMessenger/tgcalls", "url": "https://github.com/TelegramMessenger/tgcalls/commit/014653852e437a517bbb1c50063dc2518adf77f1", "title": "check reflector peer-tag length before subtracting the header size", "status": "partially fixed publicly", "disclosed": "2026-02-13", "note": "both constructors subtract four only when the raw peer tag is 16 bytes. This closes the matched length-underflow path, not every issue in the broader report. Desktop release inclusion and the full report were not independently retested.", "classification": { "area": "memory-safety", "reason": "A short peer tag must not underflow the length used for buffer operations.", "source": "https://github.com/TelegramMessenger/tgcalls/commit/014653852e437a517bbb1c50063dc2518adf77f1", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TGDESKTOP-REFLECTOR-001/", "source_url": "https://github.com/TelegramMessenger/tgcalls/commit/014653852e437a517bbb1c50063dc2518adf77f1", "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TREZOR-012", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/59d8d78ef785a60d5a01dcca974c2858ba432de2", "title": "validate the boot image buffer across the syscall boundary", "status": "fixed in public source; rollout not reverified", "disclosed": "2026-05-05", "note": "boot_image_check__verified applies probe_read_access to the image pointer and size in the syscall and smcall paths. This matches the reported buffer-validation gap, not F-TREZOR-008's JPEG path. A fixed firmware release and device rollout were not independently checked.", "classification": { "area": "authorization", "reason": "Privileged image verification must validate the memory range supplied across the caller boundary.", "source": "https://github.com/trezor/trezor-firmware/commit/59d8d78ef785a60d5a01dcca974c2858ba432de2", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-012/", "source_url": "https://github.com/trezor/trezor-firmware/commit/59d8d78ef785a60d5a01dcca974c2858ba432de2", "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-OOM-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/09d3f7386b3c42651e792aa90d959c89cee4817e", "title": "check transport progress-token length before allocating the payload buffer", "status": "partially fixed publicly", "disclosed": "2026-02-13", "note": "transportDecodeProgressToken checks data.length before subtracting 24. This matches the primary underflow vector; it does not establish fixes for every accompanying MTInputStream short-read case. The full report and release rollout were not independently retested.", "classification": { "area": "availability", "reason": "Length underflow on a short input can request an excessive allocation.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/09d3f7386b3c42651e792aa90d959c89cee4817e", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-OOM-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/09d3f7386b3c42651e792aa90d959c89cee4817e", "cwe": null, "layer": "availability" }, { "finding_id": "F-FIREFOX-AVIF-MP4PARSE-OFFSET-001", "repo": "mozilla/gecko-dev", "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020538", "title": "avoid negative sample offsets in animated AVIF decoding", "status": "fixed publicly", "patched": "Firefox 150 (vendor tracker status)", "note": "the public bug is RESOLVED FIXED and status-firefox150 is fixed. Mozilla labels it S2 and sec-other; this record does not translate S2 into a HIGH security severity or assert a CVE. The original report was not independently rerun against release binaries.", "classification": { "area": "memory-safety", "reason": "Narrowing a sample offset can produce a negative read offset in the AVIF decode stream.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020538", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-FIREFOX-AVIF-MP4PARSE-OFFSET-001/", "source_url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020538", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-SKAFFOLD-WEBHOOK-001", "repo": "GoogleContainerTools/skaffold", "url": "https://github.com/GoogleContainerTools/skaffold/commit/3e7c0304a175f6ad52524232bc26777cfd01978c", "title": "remove the GitHub preview webhook and its deployment configuration", "status": "feature removed publicly", "disclosed": "2026-03-03", "note": "PR #9999 removes the webhook implementation and associated deployment configuration, including the privileged example. This removes the reported feature from public source; it does not show that existing installations were removed or updated, or establish public attribution of this finding ID.", "classification": { "area": "authorization", "reason": "The removed preview webhook connected incoming requests to privileged deployment operations.", "source": "https://github.com/GoogleContainerTools/skaffold/commit/3e7c0304a175f6ad52524232bc26777cfd01978c", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SKAFFOLD-WEBHOOK-001/", "source_url": "https://github.com/GoogleContainerTools/skaffold/commit/3e7c0304a175f6ad52524232bc26777cfd01978c", "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-JSBRIDGE-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/687cefb2914539e2a42d3a10e91fe4ce1c7fbf7f", "title": "JSON injection in Mini App custom method response enables arbitrary JavaScript execution in WebAppWebView", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "accepted as LOW. public fix commit 687cefb2914539e2a42d3a10e91fe4ce1c7fbf7f on 2026-02-25 serializes the custom method result through JSONSerialization before sendEvent; the fix is present in release-12.5.", "classification": { "area": "semantics", "reason": "Bridge result data is interpolated into JavaScript instead of serialized.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/687cefb2914539e2a42d3a10e91fe4ce1c7fbf7f", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-JSBRIDGE-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/687cefb2914539e2a42d3a10e91fe4ce1c7fbf7f", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-TELEGRAM-E2E-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/9d33962c013e68dcecd8c26bb23ca232bc52c2a2", "title": "Non-Constant-Time Message Key Comparison in Secret Chat Decryption Violates Security Guidelines", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "accepted as LOW. public fix commit 9d33962c013e68dcecd8c26bb23ca232bc52c2a2 on 2026-02-13 replaces direct message-key comparison with constTimeIsEqual; the fix is present in release-12.5.", "classification": { "area": "confidentiality", "reason": "Message-key comparison is not constant-time.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/9d33962c013e68dcecd8c26bb23ca232bc52c2a2", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-E2E-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/9d33962c013e68dcecd8c26bb23ca232bc52c2a2", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TELEGRAM-IOS-BOTPAY-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9", "title": "WKWebView payment bridge accepts payment_form_submit from untrusted subframes without frame validation", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "accepted as LOW. public fix commit a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9 on 2026-02-13 switches the payment bridge script to forMainFrameOnly: true; the fix is present in release-12.5.", "classification": { "area": "authorization", "reason": "Payment user scripts are injected into frames outside the intended main-frame boundary.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-BOTPAY-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-WEBAPP-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-02" }, "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/c5a0ad267cbd2a61a0d4548490f6af5521fa55df", "title": "Telegram iOS Web App bridge exposed to third-party iframes", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public fix commit c5a0ad267cbd2a61a0d4548490f6af5521fa55df in release-12.4. see 1SEAL-2026-008.", "classification": { "area": "authorization", "reason": "A subframe can reach a bridge intended for the main frame.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/c5a0ad267cbd2a61a0d4548490f6af5521fa55df", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-WEBAPP-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/c5a0ad267cbd2a61a0d4548490f6af5521fa55df", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-TL-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54", "title": "heap buffer over-read in TL deserialization from operator precedence bug", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public fix commit 8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54 in release-12.4. see 1SEAL-2026-007.", "classification": { "area": "memory-safety", "reason": "TL parsing can read beyond an input buffer.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-TL-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TORVALDS-LINUX-BT-HCI-001", "repo": "torvalds/linux", "url": "https://github.com/torvalds/linux/commit/2b2bf47cd75518c36fa2d41380e4a40641cc89cd", "title": "Bluetooth: hci_event: move wake reason storage into validated event handlers", "status": "merged", "reported_via": "bluetooth maintainers", "note": "accepted into bluetooth-next: 3e7e7f4bdbe5. short HCI event frames could reach bacpy() before per-event minimum-length validation.", "cve": "CVE-2026-31771", "classification": { "area": "memory-safety", "reason": "HCI event handling lacks required buffer bounds validation.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-31771", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-HCI-001/", "source_url": "https://github.com/torvalds/linux/commit/2b2bf47cd75518c36fa2d41380e4a40641cc89cd", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TORVALDS-LINUX-TIPC-001", "repo": "torvalds/linux", "url": "https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=48a5fe38772b6f039522469ee6131a67838221a8", "title": "tipc: fix bc_ackers underflow on duplicate GRP_ACK_MSG", "status": "merged", "reported_via": "netdev maintainers", "note": "accepted upstream in netdev/net: 48a5fe38772b. duplicate or stale GRP_ACK_MSG packets could underflow bc_ackers, wrap to 65535, and leave later group broadcasts congestion-blocked until the group was recreated. stable backports are queued for 5.10-stable, 5.15-stable, 6.1-stable, and 6.6-stable.", "classification": { "area": "availability", "reason": "Duplicate acknowledgements underflow bc_ackers and block later broadcasts; no memory corruption is asserted.", "source": "https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=48a5fe38772b6f039522469ee6131a67838221a8", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-TIPC-001/", "source_url": "https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=48a5fe38772b6f039522469ee6131a67838221a8", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TORVALDS-LINUX-BT-SMP-001", "repo": "torvalds/linux", "url": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7", "title": "Bluetooth: SMP: force responder MITM requirements before building the pairing response", "status": "merged", "reported_via": "bluetooth maintainers", "note": "public mainline commits d05111bfe37b and 20756fec2f01 in torvalds/linux. the fix bundle aligns responder pairing policy and legacy STK authentication with actual MITM state. author is publicly listed as Oleh Konko with Signed-off-by.", "cve": "CVE-2026-43334 / CVE-2026-31773", "classification": { "area": "identity", "reason": "Pairing security state asserts MITM protection without establishing it.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TORVALDS-LINUX-BT-SMP-001/", "source_url": "https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-MOZILLA-FIREFOX-001", "repo": "mozilla/gecko-dev", "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2018451", "title": "WebGPU presentation sizing hardening after integer-overflow report", "status": "fixed publicly", "reported_via": "Bugzilla", "note": "bug 2018451. public fix 2f8a8fdd43a4 / autoland 67153f39ea54. public case is a hardening fix after report, not a confirmed exploitable security bug.", "classification": { "area": "memory-safety", "reason": "The change hardens WebGPU presentation-buffer size arithmetic. The vendor discussion disputes reachability of the reported overflow; this category does not assert exploitability.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2018451", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-MOZILLA-FIREFOX-001/", "source_url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2018451", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-FIREFOX-IPC-PUSH-012", "repo": "mozilla/gecko-dev", "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2022681", "title": "Push IPC observer path removed after bug 2022681 report", "status": "fixed publicly", "reported_via": "Bugzilla", "note": "bug 2022681 remains UNCONFIRMED, but the related fix bug 1862090 was resolved FIXED on 2026-03-13 with status-firefox150 = fixed. the patch removed RecvNotifyPushObservers* and the affected push IPC path. Firefox 150 shipped on 2026-04-21, so this surface is already gone in release.", "classification": { "area": "authorization", "reason": "The reported IPC path concerns binding a push scope to its principal. Classifying that boundary does not establish an exploitable cross-origin attack.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2022681", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-FIREFOX-IPC-PUSH-012/", "source_url": "https://bugzilla.mozilla.org/show_bug.cgi?id=2022681", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-OTELCOLLECTOR-001", "repo": "open-telemetry/opentelemetry-collector", "number": 15253, "url": "https://github.com/open-telemetry/opentelemetry-collector/pull/15253", "title": "[confighttp] Enforce max_request_body_size before snappy decompression", "status": "fixed publicly in v0.152.0", "reported_via": "GitHub Security Advisory GHSA-xp52-4g49-prf2", "note": "accepted private advisory opened 2026-02-23 with reporter credit to @1seal; public issue #15252 and PR #15253 fixed the confighttp snappy decode allocation-before-cap bug. release v1.58.0/v0.152.0, published 2026-05-11, includes the bugfix: Enforce max_request_body_size on Content-Encoding: snappy requests before the decoded buffer is allocated. collector-releases v0.152.0 binaries followed on 2026-05-12. fixed from v0.152.0; v0.151.x and below in the affected range should not be treated as fixed.", "classification": { "area": "availability", "reason": "The decoded Snappy size is checked before allocating the full output buffer, enforcing the configured request-body limit.", "source": "https://github.com/open-telemetry/opentelemetry-collector/pull/15253", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OTELCOLLECTOR-001/", "source_url": "https://github.com/open-telemetry/opentelemetry-collector/pull/15253", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "argoproj/argo-workflows", "number": 15466, "url": "https://github.com/argoproj/argo-workflows/pull/15466", "finding_id": "F-ARGO-ARTIFACT-001", "title": "docs: be explicit about artifact security", "status": "merged", "reported_via": "security contact", "classification": { "area": "authorization", "reason": "The public documentation places artifact access control in repository credentials rather than path restrictions in Workflows. This is authorization guidance, not a vendor-confirmed code defect.", "source": "https://github.com/argoproj/argo-workflows/pull/15466", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ARGO-ARTIFACT-001/", "source_url": "https://github.com/argoproj/argo-workflows/pull/15466", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "theupdateframework/go-tuf", "number": 721, "url": "https://github.com/theupdateframework/go-tuf/pull/721", "finding_id": "F-TUF-009", "title": "Do not allow empty hashes for the Target role", "status": "merged", "reported_via": "security contact", "classification": { "area": "integrity", "reason": "Empty target hashes are accepted without the required integrity commitment.", "source": "https://github.com/theupdateframework/go-tuf/pull/721", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TUF-009/", "source_url": "https://github.com/theupdateframework/go-tuf/pull/721", "disclosed": null, "cwe": null, "layer": "integrity" }, { "repo": "traefik/traefik", "number": 12642, "url": "https://github.com/traefik/traefik/pull/12642", "finding_id": "F-TRAEFIK-002", "title": "Validate healthcheck path configuration", "status": "merged", "reported_via": "security contact", "note": "merged into v2.11 on 2026-02-10.", "classification": { "area": "authorization", "reason": "An absolute health-check URL bypasses the intended destination boundary.", "source": "https://github.com/traefik/traefik/pull/12642", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRAEFIK-002/", "source_url": "https://github.com/traefik/traefik/pull/12642", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "traefik/traefik", "number": 12653, "url": "https://github.com/traefik/traefik/pull/12653", "finding_id": "F-TRAEFIK-002", "title": "Reject absolute URL in healthcheck path configuration", "status": "merged", "reported_via": "security contact", "note": "merged into v3.6 on 2026-02-11.", "classification": { "area": "authorization", "reason": "An absolute health-check URL bypasses the intended destination boundary.", "source": "https://github.com/traefik/traefik/pull/12642", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRAEFIK-002/", "source_url": "https://github.com/traefik/traefik/pull/12653", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-HEADSCALE-001-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "juanfont/headscale", "url": "https://github.com/juanfont/headscale/commit/4d427cfe2af6bd9bb71d1e2abcc987d2b0906e20", "title": "bound request-body reads in the machine map endpoint", "status": "fixed publicly", "reported_via": "security contact", "note": "the public fix is available in Headscale v0.29.0 and v0.29.1. no public GHSA was observed, so this is tracked as a landed fix rather than a published advisory.", "classification": { "area": "availability", "reason": "Machine-map request bodies are not bounded before processing.", "source": "https://github.com/juanfont/headscale/commit/4d427cfe2af6bd9bb71d1e2abcc987d2b0906e20", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-HEADSCALE-001-001/", "source_url": "https://github.com/juanfont/headscale/commit/4d427cfe2af6bd9bb71d1e2abcc987d2b0906e20", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-ISTIO-001", "repo": "istio/istio", "number": 59054, "url": "https://github.com/istio/istio/pull/59054", "title": "XDS debug endpoints to require authentication", "status": "fixed publicly with release-note credit", "reported_via": "security contact (email)", "note": "severity: HIGH. emailed 2026-02-02; PR #59054 merged on 2026-02-17 as the XDS debug endpoints authentication fix. fixed releases: Istio 1.27.8, 1.28.5, and 1.29.1. release/advisory notes credit: Reported by 1seal, so the earlier not-credited status is no longer current.", "classification": { "area": "identity", "reason": "XDS debug endpoints require authentication.", "source": "https://github.com/istio/istio/pull/59054", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ISTIO-001/", "source_url": "https://github.com/istio/istio/pull/59054", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-ISTIO-XDS-DEBUG-001", "repo": "istio/istio", "number": 59970, "url": "https://github.com/istio/istio/pull/59970", "title": "fix cross-namespace access in statusgen xds debug endpoints", "status": "fixed publicly with release-note credit", "reported_via": "security contact (email)", "note": "follow-up to CVE-2026-31838 / GHSA-974c-2wxh-g4ww; PR #59970 merged on 2026-04-23 and backports #59973, #59974, and #59975 for releases 1.28, 1.29, and 1.30 also merged. fixed in Istio 1.28.7, 1.29.3, and 1.30.0. release notes credit 1seal for the StatusGen XDS debug endpoint same-namespace authorization fix.", "classification": { "area": "authorization", "reason": "Debug access must be scoped to the caller's namespace.", "source": "https://github.com/istio/istio/pull/59970", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ISTIO-XDS-DEBUG-001/", "source_url": "https://github.com/istio/istio/pull/59970", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "aws/s2n-tls", "number": 5804, "url": "https://github.com/aws/s2n-tls/pull/5804", "finding_id": "F-AWS-S2N-TLS-IP-CN-001", "title": "fix: reject certs with literal-IP CN and no SAN", "status": "merged", "reported_via": "security contact (email)", "note": "separate public s2n-tls fix for the literal-IP CN and no SAN case. this is not the same public fix chain as F-AWS-LC-NAMECONSTRAINTS-001.", "classification": { "area": "identity", "reason": "The TLS verifier rejects an IP address supplied only through certificate common-name fallback without a SAN.", "source": "https://github.com/aws/s2n-tls/pull/5804", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-S2N-TLS-IP-CN-001/", "source_url": "https://github.com/aws/s2n-tls/pull/5804", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_ids": [ "F-AWS-LC-NAMECONSTRAINTS-001", "F-AWS-LC-NAMECONSTRAINTS-002" ], "repo": "aws/aws-lc", "url": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "title": "Fix CN fallback handling in name constraints checking", "status": "fixed publicly", "reported_via": "security contact (email)", "note": "public fix in aws/aws-lc on 2026-03-19 via main commit 2aa522465f69 (#3107) and fips branch commit 35bfa4362e45 (#3108). AWS linked GHSA-3jrg-j22w-mpmc and GHSA-394x-vwmw-crm3 and said CNA scope was not met; the same PRs also close the unicode CN vector tracked as F-AWS-LC-NAMECONSTRAINTS-002.", "classification": { "area": "identity", "reason": "Wildcard and Unicode common names bypass name-constraint enforcement.", "source": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-LC-NAMECONSTRAINTS-001/", "source_url": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-QEMU-001-001", "repo": "qemu/qemu", "url": "https://github.com/qemu/qemu/commit/4f28b87fdd24df2049626106b7c24d0180952115", "title": "hyperv/syndbg: check length returned by cpu_physical_memory_map()", "status": "merged", "reported_via": "private security contact", "note": "public upstream commit 4f28b87fdd24 on 2026-03-09 adds the returned-length check before writing mapped guest memory, includes Fixes: CVE-2026-3842 and Reported-by: Oleh Konko, with public backport/cherry-pick 85af4e93 on 2026-03-13.", "classification": { "area": "memory-safety", "reason": "Mapped physical-memory length is not checked before the affected access.", "source": "https://github.com/qemu/qemu/commit/4f28b87fdd24df2049626106b7c24d0180952115", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-QEMU-001-001/", "source_url": "https://github.com/qemu/qemu/commit/4f28b87fdd24df2049626106b7c24d0180952115", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-AWS-ROLESANYWHERE-GHA-001", "repo": "aws/rolesanywhere-credential-helper", "url": "https://github.com/aws/rolesanywhere-credential-helper/commit/b4207adb8856ed81710f92f7692440122ea12765", "title": "pin github actions versions", "status": "fixed publicly", "reported_via": "security contact", "note": "fixed in the release/signing path on 2026-03-10. public PR merge commit b4207adb8856 via #172, with payload commit 2e5072bf6e88.", "classification": { "area": "provenance", "reason": "CI dependencies are pinned to commit identities instead of mutable action references.", "source": "https://github.com/aws/rolesanywhere-credential-helper/commit/b4207adb8856ed81710f92f7692440122ea12765", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-ROLESANYWHERE-GHA-001/", "source_url": "https://github.com/aws/rolesanywhere-credential-helper/commit/b4207adb8856ed81710f92f7692440122ea12765", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-AWS-XRAY-DAEMON-GHA-002", "repo": "aws/aws-xray-daemon", "url": "https://github.com/aws/aws-xray-daemon/commit/4abe89b868badc59b85288d6bf74763d8ca46577", "title": "Fix SHA pinning: use correct SHAs matching original action versions", "status": "fixed publicly", "reported_via": "security contact", "note": "initial fix landed on 2026-03-12 via 135c99db10b5 (#268), then corrected/finalized on 2026-03-17 via 4abe89b868ba (#269).", "classification": { "area": "provenance", "reason": "Correcting action commit pins preserves the intended identities of CI dependencies; this is supply-chain maintenance.", "source": "https://github.com/aws/aws-xray-daemon/commit/4abe89b868badc59b85288d6bf74763d8ca46577", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-XRAY-DAEMON-GHA-002/", "source_url": "https://github.com/aws/aws-xray-daemon/commit/4abe89b868badc59b85288d6bf74763d8ca46577", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-AWS-XRAY-DAEMON-GHA-001", "repo": "aws/aws-xray-daemon", "url": "https://github.com/aws/aws-xray-daemon/commit/946763a48ab5a9be3a161598642355bc9d9e3459", "title": "Pin GitHub Action references to commit SHAs", "status": "fixed publicly", "reported_via": "security contact", "note": "same public fix chain as F-AWS-XRAY-DAEMON-GHA-002 via 135c99db10b5 and 4abe89b868ba, plus broader hardening on 2026-03-18 via 946763a48ab5 (#270).", "classification": { "area": "provenance", "reason": "CI action references are pinned to specific commits rather than mutable version tags.", "source": "https://github.com/aws/aws-xray-daemon/commit/946763a48ab5a9be3a161598642355bc9d9e3459", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-XRAY-DAEMON-GHA-001/", "source_url": "https://github.com/aws/aws-xray-daemon/commit/946763a48ab5a9be3a161598642355bc9d9e3459", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-EKSPIA-GHA-001", "repo": "aws/eks-pod-identity-agent", "url": "https://github.com/aws/eks-pod-identity-agent/commit/cdb0dd49a89fec783d7fec365ea0449222ba416e", "title": "chore: Updating action dependencies to pin to commit sha", "status": "fixed publicly", "reported_via": "security contact", "note": "fixed in the release workflow on 2026-02-05 via cdb0dd49a89f (#117).", "classification": { "area": "provenance", "reason": "CI action dependencies are bound to immutable commit identities rather than mutable tags; this is dependency-provenance hardening.", "source": "https://github.com/aws/eks-pod-identity-agent/commit/cdb0dd49a89fec783d7fec365ea0449222ba416e", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-EKSPIA-GHA-001/", "source_url": "https://github.com/aws/eks-pod-identity-agent/commit/cdb0dd49a89fec783d7fec365ea0449222ba416e", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-EKSPIA-GHA-002", "repo": "aws/eks-pod-identity-agent", "url": "https://github.com/aws/eks-pod-identity-agent/commit/dcae60b05e537055fa11315d8305f018e40dbf2e", "title": "chore: Pinning aws-actions/configure-aws-credentials to commit sha", "status": "fixed publicly", "reported_via": "security contact", "note": "follow-up fix for the remaining configure-aws-credentials reference on 2026-02-20 via dcae60b05e53 (#133).", "classification": { "area": "provenance", "reason": "The credential-configuration action is pinned to a commit identity; this is dependency-provenance hardening, not a separate confirmed exploit.", "source": "https://github.com/aws/eks-pod-identity-agent/commit/dcae60b05e537055fa11315d8305f018e40dbf2e", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-EKSPIA-GHA-002/", "source_url": "https://github.com/aws/eks-pod-identity-agent/commit/dcae60b05e537055fa11315d8305f018e40dbf2e", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-AWS-CW-AGENT-GHA-001", "repo": "aws/amazon-cloudwatch-agent", "url": "https://github.com/aws/amazon-cloudwatch-agent/pull/2071", "title": "Pin GitHub Actions to commit SHAs", "status": "fixed publicly", "reported_via": "security contact", "note": "fixed by #2071, merged 2026-04-01, merge commit e360ba430b55.", "classification": { "area": "provenance", "reason": "CI action dependencies are bound to immutable commit identities rather than mutable tags; this is dependency-provenance hardening.", "source": "https://github.com/aws/amazon-cloudwatch-agent/pull/2071", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-CW-AGENT-GHA-001/", "source_url": "https://github.com/aws/amazon-cloudwatch-agent/pull/2071", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-KARPENTER-TOOLCHAIN-001", "repo": "aws/karpenter-provider-aws", "url": "https://github.com/aws/karpenter-provider-aws/pull/9038", "title": "ci: remove latest from toolchain", "status": "fixed publicly", "reported_via": "security contact", "note": "fixed by #9038, merged 2026-03-27, merge commit efb5ea52a479.", "classification": { "area": "provenance", "reason": "Build tools use explicit versions instead of latest, constraining which dependencies enter the toolchain.", "source": "https://github.com/aws/karpenter-provider-aws/pull/9038", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-KARPENTER-TOOLCHAIN-001/", "source_url": "https://github.com/aws/karpenter-provider-aws/pull/9038", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-SOCI-OOB-001", "repo": "awslabs/soci-snapshotter", "url": "https://github.com/awslabs/soci-snapshotter/commit/0a1984bb2ffb169a0d11d543a6dde85dfd6ba506", "title": "Fast-fail on incorrect MaxSpanID", "status": "fixed publicly", "reported_via": "security contact", "note": "fixed by #1916, merged 2026-04-01, merge commit 0a1984bb2ffb. AWS said it was still determining whether a GHSA would be published.", "classification": { "area": "memory-safety", "reason": "The span manager validates MaxSpanID against checkpoint and digest counts before indexing span data.", "source": "https://github.com/awslabs/soci-snapshotter/commit/0a1984bb2ffb169a0d11d543a6dde85dfd6ba506", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SOCI-OOB-001/", "source_url": "https://github.com/awslabs/soci-snapshotter/commit/0a1984bb2ffb169a0d11d543a6dde85dfd6ba506", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-AWSRUST-CACHE-001", "repo": "smithy-lang/smithy-rs", "number": 4584, "url": "https://github.com/smithy-lang/smithy-rs/pull/4584", "title": "Update standard FS impl to write files with `0o600` permissions", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix PR #4584 merged on 2026-03-27. updates unix cache-file writes to owner-only `0o600` permissions; AWS advised no separate advisory will be published.", "classification": { "area": "authorization", "reason": "Credential-cache files receive owner-only permissions on Unix, restricting access by other local users.", "source": "https://github.com/smithy-lang/smithy-rs/pull/4584", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWSRUST-CACHE-001/", "source_url": "https://github.com/smithy-lang/smithy-rs/pull/4584", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-CEDAR-PST-ERRORCONSTRAINT-001", "repo": "cedar-policy/cedar", "url": "https://github.com/cedar-policy/cedar/pull/2246", "title": "PST fail-closed + protobuf compatibility fix", "status": "fixed publicly", "reported_via": "security contact", "note": "public fixes #2246 and #2247 merged on 2026-03-23. AWS stated no customer action was required because the affected paths needed two experimental flags enabled together and were not used in AWS authorization paths.", "classification": { "area": "semantics", "reason": "Serialization changes an invalid action constraint into a match-all constraint, so the decoded policy no longer means the original policy. The experimental-feature and deployment limits remain in the record.", "source": "https://github.com/cedar-policy/cedar/pull/2246", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CEDAR-PST-ERRORCONSTRAINT-001/", "source_url": "https://github.com/cedar-policy/cedar/pull/2246", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-PURPLELLAMA-003", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "meta-llama/PurpleLlama", "url": "https://github.com/meta-llama/PurpleLlama/commit/48fa920b7acee37eb7acce2c797f7faded6213a0", "title": "Fix RCE for canary exploit", "status": "fixed on main (release not confirmed)", "reported_via": "security contact", "note": "The canary-exploit benchmark parsed model-response values with eval(), allowing input data to be evaluated as Python when that benchmark path ran. Commit 48fa920b of 11 March 2026 replaces those evaluations with ast.literal_eval() in verify_response.py. This confirms the recorded code/data-boundary change in public source, not a separately identified stable release or deployment. The existing finding is retained once, without adding another result for this recheck. A maintainer confirmation tying the patch to this report and public reporter credit remain unconfirmed.", "classification": { "area": "semantics", "reason": "Replacing eval with literal parsing keeps model-response data from being interpreted as executable Python.", "source": "https://github.com/meta-llama/PurpleLlama/commit/48fa920b7acee37eb7acce2c797f7faded6213a0", "reviewed": "2026-09-26" }, "patched": "public source commit; a separate fixed release is not established", "source_reviewed": "2026-09-26", "related_sources": [ { "label": "Patched benchmark response parser", "url": "https://github.com/meta-llama/PurpleLlama/blob/48fa920b7acee37eb7acce2c797f7faded6213a0/CybersecurityBenchmarks/datasets/canary_exploit/verify_response.py" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PURPLELLAMA-003/", "source_url": "https://github.com/meta-llama/PurpleLlama/commit/48fa920b7acee37eb7acce2c797f7faded6213a0", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-DENO-001-001", "repo": "denoland/deno", "number": 33203, "url": "https://github.com/denoland/deno/pull/33203", "title": "fix(permissions): check deny rules against resolved IPs to prevent numeric hostname bypass", "status": "fixed publicly in v2.7.12; Node compat follow-up in v2.8.0", "reported_via": "security advisory", "note": "accepted on 2026-03-05. public fix PR #33203 merged on 2026-04-09 and shipped in Deno v2.7.12 on 2026-04-09; the release notes include fix(permissions): check deny rules against resolved IPs to prevent numeric hostname bypass. Deno later closed the Node TCP compatibility path through PR #33880, merged on 2026-05-07, which adds a post-resolution deny check in TCPWrap connect and shipped in Deno v2.8.0. internal advisory metadata credits @1seal as reporter, but public credit is not yet confirmed. GHSA id provided in the disclosure thread: GHSA-j65g-6x8f-87c5; the public advisory URL is not currently reachable.", "classification": { "area": "authorization", "reason": "Network deny rules are applied to resolved IP addresses, preventing numeric hostnames from bypassing configured permissions.", "source": "https://github.com/denoland/deno/pull/33203", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-DENO-001-001/", "source_url": "https://github.com/denoland/deno/pull/33203", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-SIGNAL-DESKTOP-EXPIRE-001", "repo": "signalapp/Signal-Desktop", "url": "https://github.com/signalapp/Signal-Desktop/commit/c863dfa66bdfdf636d9a218cdd263b0cc997fb1a", "title": "Ignore expireTimerVersion=0 messages", "status": "fixed publicly", "reported_via": "security contact", "note": "A zero expiration-timer version could enter conversation timer-state handling instead of being rejected as an invalid version. The public fix chain began with serialization changes on 10 March 2026; commit c863dfa6 of 20 March adds the explicit version === 0 rejection. That check is present in stable v8.5.0, not just the previously recorded 8.10.0 alpha; inspected v8.4.1 still lacks it. This addresses the zero-version state-update path, not a guarantee that conversation participants cannot legitimately change a disappearing-message timer. Source and release inspection do not establish rollout to every desktop installation.", "classification": { "area": "integrity", "reason": "Rejecting zero or stale expiration-timer versions preserves the ordering and integrity of conversation timer state.", "source": "https://github.com/signalapp/Signal-Desktop/commit/c863dfa66bdfdf636d9a218cdd263b0cc997fb1a", "reviewed": "2026-09-26" }, "patched": "v8.5.0", "source_reviewed": "2026-09-26", "related_sources": [ { "label": "v8.5.0: zero-version rejection", "url": "https://github.com/signalapp/Signal-Desktop/blob/v8.5.0/ts/models/conversations.preload.ts" }, { "label": "v8.5.0 release", "url": "https://github.com/signalapp/Signal-Desktop/releases/tag/v8.5.0" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIGNAL-DESKTOP-EXPIRE-001/", "source_url": "https://github.com/signalapp/Signal-Desktop/commit/c863dfa66bdfdf636d9a218cdd263b0cc997fb1a", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-LEDGER-ETH-GCS-CLEANUP-DOUBLEFREE-001", "repo": "LedgerHQ/app-ethereum", "url": "https://github.com/LedgerHQ/app-ethereum/commit/601c828", "title": "Fix 'use-after-free' or 'double-free' issues", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 601c828 landed on 2026-04-01. the first public release confirmed to contain the fix is app-ethereum 1.22.0, released on 2026-04-15.", "classification": { "area": "memory-safety", "reason": "Clear-signing cleanup can free the same allocation twice.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/601c828", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-ETH-GCS-CLEANUP-DOUBLEFREE-001/", "source_url": "https://github.com/LedgerHQ/app-ethereum/commit/601c828", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-ETH-EIP712-CALLDATA-001", "repo": "LedgerHQ/app-ethereum", "url": "https://github.com/LedgerHQ/app-ethereum/commit/d61639c", "title": "Fixed dead condition in EIP-712 calldata filtering code", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit d61639c landed on 2026-03-24. the fix shipped in app-ethereum 1.22.0, released on 2026-04-15.", "classification": { "area": "semantics", "reason": "An ineffective calldata filter breaks the intended clear-signing display boundary.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/d61639c", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-ETH-EIP712-CALLDATA-001/", "source_url": "https://github.com/LedgerHQ/app-ethereum/commit/d61639c", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-TELEGRAM-DESKTOP-FILENAME-TRAVERSAL-001", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/82f9aa1a2a0970e48caf8d7f4a60284347a13d99", "title": "Fixed path traversal in bulk file download via filename sanitization.", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit 82f9aa1a2a09 on 2026-03-31 sanitizes document filenames through FileNameFromUserString(...) in the affected bulk-download path.", "classification": { "area": "authorization", "reason": "Untrusted filenames require sanitization before local path use.", "source": "https://github.com/telegramdesktop/tdesktop/commit/82f9aa1a2a0970e48caf8d7f4a60284347a13d99", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-DESKTOP-FILENAME-TRAVERSAL-001/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/82f9aa1a2a0970e48caf8d7f4a60284347a13d99", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TGAND-SECRETCHAT-VECTOR-001", "repo": "DrKLO/Telegram", "url": "https://github.com/DrKLO/Telegram/commit/fb98f157afb3e5048bce4a9496104e5aed557686", "title": "update to 12.6.2 (6655)", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public android commit fb98f157afb3 on 2026-04-05 (12.6.2) adds validateSize(...) checks in the affected Vector.java path and appears to close the reported secret-chat vector-size issue.", "classification": { "area": "availability", "reason": "Rejecting invalid vector sizes prevents malformed secret-chat input from reaching excessive allocation or parser failure; native memory corruption is not established here.", "source": "https://github.com/DrKLO/Telegram/commit/fb98f157afb3e5048bce4a9496104e5aed557686", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TGAND-SECRETCHAT-VECTOR-001/", "source_url": "https://github.com/DrKLO/Telegram/commit/fb98f157afb3e5048bce4a9496104e5aed557686", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_ids": [ "F-TGAND-GIFVIDEO-OOB-001", "F-TGAND-GIFVIDEO-001" ], "repo": "DrKLO/Telegram", "url": "https://github.com/DrKLO/Telegram/commit/63f86ef", "title": "update to 12.7.0 (6740)", "status": "fixed publicly (mapped by code area)", "reported_via": "Telegram security contact", "note": "public Android 12.7.0 commit 63f86ef on 2026-05-21 updates the native gifvideo.cpp history. the fix is mapped with high confidence to the GIF/video OOB class because the path is hardened around SwsContextHolder, bitmapStride handling, and sws recreation on size/format changes.", "classification": { "area": "memory-safety", "reason": "Stride and conversion-context handling can access outside native video buffers. Stride and conversion-context handling can access outside native video buffers; the related ID remains separately recorded.", "source": "https://github.com/DrKLO/Telegram/commit/63f86ef", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TGAND-GIFVIDEO-OOB-001/", "source_url": "https://github.com/DrKLO/Telegram/commit/63f86ef", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TELEGRAM-DESKTOP-FFMPEG-LINESIZE-MEMCPY-001", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "title": "More strict checks in ffmpeg decodiing.", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit eeafe9761409 on 2026-04-07 adds stricter negative-linesize handling in the affected ffmpeg render path.", "classification": { "area": "memory-safety", "reason": "A negative or invalid frame stride reaches a raw memory copy.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-DESKTOP-FFMPEG-LINESIZE-MEMCPY-001/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TGX-PATHTRAVERSAL-001", "repo": "TGX-Android/Telegram-X", "url": "https://github.com/TGX-Android/Telegram-X/commit/c3b01454df69", "title": "Upgrade TDLib to tdlib/td@8fc2344", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit c3b01454df69 on 2026-05-03 updates U.java so getSecureFileName returns the sanitized buffer via b.toString() instead of the original fileName string, closing the path traversal sink.", "classification": { "area": "authorization", "reason": "Filename handling returns the original rather than sanitized name.", "source": "https://github.com/TGX-Android/Telegram-X/commit/c3b01454df69", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TGX-PATHTRAVERSAL-001/", "source_url": "https://github.com/TGX-Android/Telegram-X/commit/c3b01454df69", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-IOS-SSRF-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/6eb201465096", "title": "Fix web", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit 6eb201465096 on 2026-04-29 adds allowed-bot-media URL validation with canonical IPv4 parsing and public IPv4/IPv6 checks before Web App media_url fetches.", "classification": { "area": "authorization", "reason": "Bot media URLs bypass the intended public-network destination boundary.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/6eb201465096", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-SSRF-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/6eb201465096", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-IOS-FFMPEG-LINESIZE-MEMCPY-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "title": "Update tgcalls", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commits 615becca7ae7 and 9ed75ca048e7 on 2026-04-21 add isPlanarYUV420Safe() before memcpy paths, rejecting negative frame.lineSize[0..3] for the affected ffmpeg decoded-frame flows.", "classification": { "area": "memory-safety", "reason": "Negative frame strides reach planar copy/convert paths.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-FFMPEG-LINESIZE-MEMCPY-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TELEGRAM-IOS-FFMPEG-PREVIEW-PIXFMT-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "title": "Update tgcalls", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commits 615becca7ae7 and 9ed75ca048e7 on 2026-04-21 add isPlanarYUV420Safe(), including a format guard that blocks non-YUV/YUVA planar-420 layouts from the preview conversion and planar copy paths.", "classification": { "area": "memory-safety", "reason": "Unsupported pixel layouts reach a conversion path that assumes planar YUV data.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-FFMPEG-PREVIEW-PIXFMT-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TELEGRAM-IOS-SECRETAPI-LOCKOUT-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/2dd07ef8cc79", "title": "TelegramApi: regenerate Api*/SecretApiLayer*.swift with safe flag unwrap", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit 2dd07ef8cc79 on 2026-04-21 replaces Int(_1!) flag checks with Int(_1 ?? 0), removing the SecretApiLayer force-unwrap crash on truncated decryptedMessage inputs.", "classification": { "area": "availability", "reason": "Truncated secret-message flags reach a force unwrap.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/2dd07ef8cc79", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-SECRETAPI-LOCKOUT-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/2dd07ef8cc79", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TELEGRAM-IOS-TGLINK-001", "repo": "TelegramMessenger/Telegram-iOS", "url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/cbf8f6b", "title": "Filter url", "status": "fixed publicly (mapped by code area)", "reported_via": "Telegram security contact", "note": "public iOS commit cbf8f6b on 2026-06-04 removes the special tg-link hostoverride handler from OpenUrl.swift. this is mapped as fixed for the reported TGLINK host-override class.", "classification": { "area": "authorization", "reason": "The removed URL-controlled host override concerns who may choose an application endpoint. This classifies the public change only; the exact report-to-fix mapping remains conditional.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/cbf8f6b", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-TGLINK-001/", "source_url": "https://github.com/TelegramMessenger/Telegram-iOS/commit/cbf8f6b", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-IOS-TGCALLS-SIGNALING-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "TelegramMessenger/tgcalls", "url": "https://github.com/TelegramMessenger/tgcalls/commit/24fd51b", "title": "feat: SCTP signaling improvements for reliable connection establishment", "status": "fixed publicly (upstream tgcalls)", "reported_via": "Telegram security contact", "note": "public tgcalls commit 24fd51b on 2026-04-15 adds SCTP signaling reliability fixes, including writable gating and timer backoff bounds. Telegram iOS later pulled a tgcalls submodule revision that includes this fix.", "classification": { "area": "availability", "reason": "Bounded retry timing and write gating concern signaling availability; this does not independently confirm the report-to-fix mapping.", "source": "https://github.com/TelegramMessenger/tgcalls/commit/24fd51b", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-IOS-TGCALLS-SIGNALING-001/", "source_url": "https://github.com/TelegramMessenger/tgcalls/commit/24fd51b", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TELEGRAM-INTOVF-001", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "title": "More strict checks in ffmpeg decodiing.", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commits eeafe9761409 on 2026-04-07 and 9eda44ca316b on 2026-04-30 add stricter ffmpeg linesize handling, ValidFrameSize checks, max_pixels propagation, and null-allocation failure handling for the reported integer-overflow paths.", "classification": { "area": "memory-safety", "reason": "Frame size/stride arithmetic is used before bounded frame storage checks.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-INTOVF-001/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "title": "More strict checks in ffmpeg decodiing.", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public commit eeafe9761409 on 2026-04-07 adds decoded frame area guards; follow-up commit 9eda44ca316b on 2026-04-30 strengthens frame-size validation with ValidFrameSize and max_pixels handling for the same ffmpeg frame-size class.", "classification": { "area": "availability", "reason": "The decoded frame-area guard bounds frame storage allocation, protecting decoder availability; this record does not independently establish memory corruption.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TELEGRAM-WEBK-TGIV-DECODE-001", "repo": "morethanwords/tweb", "url": "https://github.com/morethanwords/tweb/commit/6af7087389c08e9860ce17559915a7747ac99ac0", "title": "restrict tg://iv decode to safe links", "status": "fixed publicly", "reported_via": "Telegram security contact", "note": "public WebK/tweb commit 6af7087389c0 restricts tg://iv local decode handling to safe links; unsafe or broken links no longer keep the local handler.", "classification": { "area": "semantics", "reason": "The tg://iv decoder distinguishes trusted link data from unsafe input before enabling local URL handling.", "source": "https://github.com/morethanwords/tweb/commit/6af7087389c08e9860ce17559915a7747ac99ac0", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-WEBK-TGIV-DECODE-001/", "source_url": "https://github.com/morethanwords/tweb/commit/6af7087389c08e9860ce17559915a7747ac99ac0", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-TGDESKTOP-WEBVIEW-004", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/55768ee", "title": "Harden interaction app<->shell<->webapp.", "status": "likely fixed publicly (mapped by hardening area)", "reported_via": "Telegram security contact", "note": "public tdesktop commit 55768ee on 2026-05-15 hardens the app<->shell<->webapp interaction across bot_webview_shell_html, attach_bot_webview, and lib_webview paths. this is mapped as a likely fix for F-TGDESKTOP-WEBVIEW-004; later same-origin webapp support also appears in the 6.8.x release line.", "classification": { "area": "authorization", "reason": "The public hardening constrains app, shell and WebApp interaction origins, an authorization boundary. Coverage of the exact report remains qualified.", "source": "https://github.com/telegramdesktop/tdesktop/commit/55768ee", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TGDESKTOP-WEBVIEW-004/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/55768ee", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-WEBA-POSTMSG-001", "repo": "Ajaxy/telegram-tt", "url": "https://github.com/Ajaxy/telegram-tt/commit/7e789e6", "title": "General: Better validation for iframe event origins (#6856)", "status": "partially likely fixed publicly (re-test needed)", "reported_via": "Telegram security contact", "note": "public WebA commit 7e789e6 on 2026-04-17 adds isMessageFromIframe(...) checks so iframe events are accepted only from the expected iframe. caveat: outbound postMessage(..., '*') patterns may still exist, so this is tracked as partial/likely fixed pending re-test if the original issue was specifically targetOrigin='*'.", "classification": { "area": "authorization", "reason": "Incoming iframe events are bound to the intended source, restricting who can invoke the message handler. This does not establish coverage of outbound targetOrigin behavior.", "source": "https://github.com/Ajaxy/telegram-tt/commit/7e789e6", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-WEBA-POSTMSG-001/", "source_url": "https://github.com/Ajaxy/telegram-tt/commit/7e789e6", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-GO-ATTESTATION-001", "repo": "google/go-attestation", "url": "https://github.com/google/go-attestation/commit/becfd074e9ceded0e5e4cc56f3eb25d43e930c00", "title": "attest: fix uint32 underflow in parseEfiSignatureList", "status": "fixed publicly", "reported_via": "security contact", "note": "public issue #485, PR #486, merged on 2026-03-06. upstream added the lower-bound validation for malformed EFI_SIGNATURE_LIST parsing in parseEfiSignatureList.", "classification": { "area": "availability", "reason": "Malformed EFI signature-list lengths can cause an infinite loop or an approximately 4 GiB allocation and OOM panic. The checked Go parser therefore concerns availability, not established memory corruption.", "source": "https://github.com/google/go-attestation/commit/becfd074e9ceded0e5e4cc56f3eb25d43e930c00", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-ATTESTATION-001/", "source_url": "https://github.com/google/go-attestation/commit/becfd074e9ceded0e5e4cc56f3eb25d43e930c00", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-FLUTTER-APNG-001", "repo": "flutter/flutter", "url": "https://github.com/flutter/flutter/pull/186700", "title": "Fix a potential buffer overflow in the animated PNG decoder when parsing malformed fdAT chunks", "status": "fixed publicly", "reported_via": "public Flutter PR", "note": "merged on 2026-05-21 as commit 9cf97ce9d21d. maintainer note says the fix is based on #184301 and our #183180; it rejects malformed fdAT chunks with data_length below the 4-byte sequence-number minimum. stable cherry-pick #188038 merged to flutter-3.44-candidate.0 on 2026-06-18 as commit a4ce257.", "classification": { "area": "memory-safety", "reason": "The APNG decoder rejects fdAT chunks shorter than the four-byte prefix before payload-length arithmetic.", "source": "https://github.com/flutter/flutter/pull/186700", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-FLUTTER-APNG-001/", "source_url": "https://github.com/flutter/flutter/pull/186700", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-PROTOBUF-UPB-STRTOF-LOCALE-OVERFLOW-001", "repo": "protocolbuffers/protobuf", "url": "https://github.com/protocolbuffers/protobuf/commit/880f66e172347ac432dd5a2c07c38aa67dc95813", "title": "upb: add bounds check to LocalizeRadix()", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 880f66e17234 on 2026-03-23. commit message states: closes a memory corruption vulnerability. release v34.1 from 2026-03-19 still predates the fix.", "classification": { "area": "memory-safety", "reason": "Locale radix conversion receives explicit output-buffer bounds instead of unchecked copying.", "source": "https://github.com/protocolbuffers/protobuf/commit/880f66e172347ac432dd5a2c07c38aa67dc95813", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTOBUF-UPB-STRTOF-LOCALE-OVERFLOW-001/", "source_url": "https://github.com/protocolbuffers/protobuf/commit/880f66e172347ac432dd5a2c07c38aa67dc95813", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-NGINX-HTTP-REQ-002", "repo": "nginx/nginx", "url": "https://github.com/nginx/nginx/commit/f405ef11fde6ed749318a844c010ce97483a8f98", "title": "bare LF accepted in chunked transfer encoding", "status": "fixed publicly", "reported_via": "private security contact", "note": "public fix commit f405ef11fde6 on 2025-12-06, first released in nginx 1.29.4 on 2025-12-09. stable 1.28.x appears unpatched as of 1.28.3 (2026-03-24).", "classification": { "area": "semantics", "reason": "Rejecting bare LF in chunked encoding tightens HTTP message framing and avoids divergent interpretations of request boundaries.", "source": "https://github.com/nginx/nginx/commit/f405ef11fde6ed749318a844c010ce97483a8f98", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NGINX-HTTP-REQ-002/", "source_url": "https://github.com/nginx/nginx/commit/f405ef11fde6ed749318a844c010ce97483a8f98", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-APISIX-CLS-HTTP-001", "repo": "apache/apisix", "url": "https://github.com/apache/apisix/commit/f609ea332af7333acebc04bd20c2878233285129", "title": "feat: make scheme configurable with default set to https", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit f609ea332af7 appears to address the reported issue.", "classification": { "area": "confidentiality", "reason": "The logging plugin defaults to HTTPS rather than plaintext HTTP for its outbound transport.", "source": "https://github.com/apache/apisix/commit/f609ea332af7333acebc04bd20c2878233285129", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-APISIX-CLS-HTTP-001/", "source_url": "https://github.com/apache/apisix/commit/f609ea332af7333acebc04bd20c2878233285129", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-APISIX-OIDC-TLS-001", "repo": "apache/apisix", "url": "https://github.com/apache/apisix/commit/dd42b19feb15d12b0f6dbfbfdae6f4f2207d0f2c", "title": "chore: set default value of ssl_verify to true", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit dd42b19feb15 appears to address the reported issue.", "classification": { "area": "identity", "reason": "TLS certificate verification defaults to enabled for the OpenID provider and Redis session endpoint.", "source": "https://github.com/apache/apisix/commit/dd42b19feb15d12b0f6dbfbfdae6f4f2207d0f2c", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-APISIX-OIDC-TLS-001/", "source_url": "https://github.com/apache/apisix/commit/dd42b19feb15d12b0f6dbfbfdae6f4f2207d0f2c", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-TRIVY-CONFIG-TEMPLATE-001", "repo": "aquasecurity/trivy", "url": "https://github.com/aquasecurity/trivy/commit/20458b836b71b2bed72d31ebba1ba9572333dcfd", "title": "fix(flag): validate template file extension", "status": "fixed publicly", "reported_via": "private reporting channel", "note": "public remediation commit 20458b836b71 appears to address the earlier repo-local template/config issue.", "classification": { "area": "unclassified", "reason": "The public title names a template-extension check, but does not establish the report's exact execution or path mechanism.", "source": "https://github.com/aquasecurity/trivy/commit/20458b836b71b2bed72d31ebba1ba9572333dcfd", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRIVY-CONFIG-TEMPLATE-001/", "source_url": "https://github.com/aquasecurity/trivy/commit/20458b836b71b2bed72d31ebba1ba9572333dcfd", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-SMALLSTEP-AK-EKU-001", "repo": "smallstep/certificates", "url": "https://github.com/smallstep/certificates/pull/2569", "title": "Validate tcg-kp-AIKCertificate EKU", "status": "fixed publicly", "reported_via": "security contact", "note": "TPM attestation EKU panic. public fix PR #2569, first released in v0.30.0. GHSA-9qq8-cgcv-qmc9 / CVE-2026-40097 published.", "classification": { "area": "availability", "reason": "An empty EKU input reaches a panic, not an established authorization bypass.", "source": "https://github.com/smallstep/certificates/pull/2569", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SMALLSTEP-AK-EKU-001/", "source_url": "https://github.com/smallstep/certificates/pull/2569", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-SMALLSTEP-WEBHOOK-001", "repo": "smallstep/certificates", "url": "https://github.com/smallstep/certificates/pull/2570", "title": "Validate webhooks", "status": "fixed publicly", "reported_via": "security contact", "note": "request-influenced webhook destination rendering. public fix PR #2570, first released in v0.30.0.", "classification": { "area": "authorization", "reason": "Request-influenced webhook rendering controls the outbound destination.", "source": "https://github.com/smallstep/certificates/pull/2570", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SMALLSTEP-WEBHOOK-001/", "source_url": "https://github.com/smallstep/certificates/pull/2570", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-LIBSIGNAL-JNI-DESTROY-UB-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "signalapp/libsignal", "url": "https://github.com/signalapp/libsignal/commit/895b079448396c1d0ba051de4f2b5b5fea64d5ef", "title": "jni: Avoid forming &mut when destroying a bridged handle", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 895b07944839 on 2026-03-13, first released in v0.89.0 on 2026-03-17.", "classification": { "area": "memory-safety", "reason": "JNI handle destruction avoids forming an unnecessary mutable reference, reducing invalid aliasing and lifetime assumptions.", "source": "https://github.com/signalapp/libsignal/commit/895b079448396c1d0ba051de4f2b5b5fea64d5ef", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LIBSIGNAL-JNI-DESTROY-UB-001/", "source_url": "https://github.com/signalapp/libsignal/commit/895b079448396c1d0ba051de4f2b5b5fea64d5ef", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-GNUPG-001-002", "repo": "gnupg/gnupg", "url": "https://github.com/sailfishos-mirror/gnupg/commit/7a2692fe5e580ae3bbb2a47abc4baaf1af65aa88", "title": "tool:gpgtar: Check the output directory with --directory.", "status": "fixed publicly", "reported_via": "private reporting channel", "note": "public GnuPG T8159 tracks gpgtar write outside --directory via symlink traversal with Reported-by: Oleh Konko; commit 7a2692fe5e58 landed on 2026-03-24 and GnuPG 2.5.19 announced the fix for gpgtar -C/--directory output-directory checking on 2026-04-24. CVE-2026-105712 was published on 2026-10-05 for this gpgtar issue.", "classification": { "area": "authorization", "reason": "gpgtar checks that the requested extraction directory is empty and not a symlink before writing plaintext files.", "source": "https://github.com/sailfishos-mirror/gnupg/commit/7a2692fe5e580ae3bbb2a47abc4baaf1af65aa88", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GNUPG-001-002/", "source_url": "https://github.com/sailfishos-mirror/gnupg/commit/7a2692fe5e580ae3bbb2a47abc4baaf1af65aa88", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-CONFLUENTIC-SCHEMA-REGISTRY-REST-BODY-NOCAP-001", "repo": "confluentinc/schema-registry", "url": "https://github.com/confluentinc/schema-registry/commit/bd56596", "title": "add size limit handler to limit req/resp size (#4310) (#4313)", "status": "fixed publicly", "reported_via": "private security contact", "note": "public commit bd56596 on 2026-05-18 adds Jetty SizeLimitHandler, size.limit.handler.enabled and max.request.body.size configuration, plus RestApiRequestBodySizeClusterTest coverage for HTTP 413 on oversized request bodies. releases v8.0.6, v8.1.4, v8.2.2, and v8.3.0 contain the fix; v8.0.6 was tagged 2026-06-19.", "classification": { "area": "availability", "reason": "A configurable body-size handler bounds request/response buffering; the inspected patch leaves this control disabled by default.", "source": "https://github.com/confluentinc/schema-registry/commit/bd56596", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-CONFLUENTIC-SCHEMA-REGISTRY-REST-BODY-NOCAP-001/", "source_url": "https://github.com/confluentinc/schema-registry/commit/bd56596", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TRTLLM-DESER-001", "repo": "NVIDIA/TensorRT-LLM", "url": "https://nvidia.custhelp.com/app/answers/detail/a_id/5805/~/security-bulletin%3A-nvidia-tensorrt-llm---may-2026", "title": "Security Bulletin: NVIDIA TensorRT-LLM - May 2026", "status": "fixed publicly (mapped to unsafe deserialization class)", "reported_via": "NVIDIA security contact", "note": "NVIDIA TensorRT-LLM May 2026 bulletin lists unsafe deserialization CVE-2025-33255 and CVE-2026-24163 as fixed for versions prior to v1.2, and recommends TensorRT-LLM v1.2.1. this is mapped to F-TRTLLM-DESER-001 if the private report corresponds to the unsafe deserialization class; public acknowledgement credits a different reporter, so this is tracked as reported-fix mapping rather than public CVE credit.", "classification": { "area": "unclassified", "reason": "The public bulletin-to-finding mapping is conditional and the bulletin could not be retrieved during this review. Its general deserialization class is not enough to classify this exact report.", "source": "https://nvidia.custhelp.com/app/answers/detail/a_id/5805/~/security-bulletin%3A-nvidia-tensorrt-llm---may-2026", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRTLLM-DESER-001/", "source_url": "https://nvidia.custhelp.com/app/answers/detail/a_id/5805/~/security-bulletin%3A-nvidia-tensorrt-llm---may-2026", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-ACROSS-009-001", "repo": "across-protocol/contracts", "url": "https://github.com/across-protocol/contracts/pull/1405", "title": "chore: deploy Polygon_SpokePool", "status": "fixed and deployed publicly", "reported_via": "private security contact", "note": "nested tryMulticall bypass in Polygon_SpokePool multicall validation. initial PR #1363 added commit 3d163b8 on 2026-03-11 to block MultiCallerUpgradeable.tryMulticall.selector alongside multicall.selector, then closed unmerged for audit. PR #1405 merged the same fix on 2026-04-08 via merge commit 5388448 and deployed a new Polygon_SpokePool implementation. Across docs list Polygon chain id 137 SpokePool proxy 0x9295...F096; verified production implementation mapping reported as 0x4a84a43274f5f99e94aa0ebef53bc06af8bc3dfb.", "classification": { "area": "authorization", "reason": "Nested tryMulticall is added to the forbidden selectors so call nesting cannot bypass the Polygon SpokePool operation guard.", "source": "https://github.com/across-protocol/contracts/pull/1405", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ACROSS-009-001/", "source_url": "https://github.com/across-protocol/contracts/pull/1405", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-MOBY-001-001", "repo": "moby/moby", "url": "https://github.com/moby/moby/commit/7a767b27fd1238c89a5cc926c39e27d3bcf58e35", "title": "pkg/authz: Reject requests exceeding body size limit", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 7a767b27fd12 appears to address the reported issue. GHSA-x744-4wpc-v9h2 / CVE-2026-34040 published with credit to 1seal / Oleh Konko.", "classification": { "area": "authorization", "reason": "An oversized request body bypasses the authorization plugin decision.", "source": "https://github.com/moby/moby/commit/7a767b27fd1238c89a5cc926c39e27d3bcf58e35", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-MOBY-001-001/", "source_url": "https://github.com/moby/moby/commit/7a767b27fd1238c89a5cc926c39e27d3bcf58e35", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-DECRED-DCRD-RPC-LIMITED-ONLY-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "decred/dcrd", "url": "https://github.com/decred/dcrd/commit/2d6b77049f1c529fb9c40099098c64a863825e7b", "title": "rpcserver: Ensure limited user is always limited", "status": "fixed publicly", "reported_via": "security contact", "patched": "dcrd v2.1.4 (release-v2.1.4)", "source_reviewed": "2026-09-26", "note": "public master fix commit 2d6b77049f1c on 2026-03-10. the official dcrd release-v2.1.4 notes, published on 2026-04-07, include the limited-user authentication fix via PR #3660: https://github.com/decred/dcrd/releases/tag/release-v2.1.4. this corrects the previously recorded v1.10.6 version; v2.1.4 is a verified release containing the fix, not a claim about the earliest fixed version on every branch. the change prevents limited-only access from gaining administrator privileges when admin auth is unset.", "classification": { "area": "authorization", "reason": "A limited RPC account must not gain administrator access when administrator credentials are unset.", "source": "https://github.com/decred/dcrd/commit/2d6b77049f1c529fb9c40099098c64a863825e7b", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-DECRED-DCRD-RPC-LIMITED-ONLY-001/", "source_url": "https://github.com/decred/dcrd/commit/2d6b77049f1c529fb9c40099098c64a863825e7b", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-DCRWALLET-001", "repo": "decred/dcrwallet", "url": "https://github.com/decred/dcrwallet/pull/2617", "title": "jsonrpc: Fix bugs in authenticate RPC.", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix PR #2617 merged on 2026-04-06. closes fail-open handling in the authenticate RPC path where ParseParams and the cmd type assertion could incorrectly treat bad credentials as not invalid.", "classification": { "area": "identity", "reason": "Malformed authenticate RPC input can avoid the invalid-credentials decision.", "source": "https://github.com/decred/dcrwallet/pull/2617", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-DCRWALLET-001/", "source_url": "https://github.com/decred/dcrwallet/pull/2617", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-PROTON-WEBCL-001", "repo": "ProtonMail/WebClients", "url": "https://github.com/ProtonMail/WebClients/blob/008dfe64b21da7e0d64bc21572b5cbacb09deeab/packages/mail-renderer/helpers/getIframeHtml.ts", "title": "sanitize iframe bodyClasses and bodyStyles in getIframeHtml", "status": "fixed in public source; rollout not reverified", "reported_via": "security contact", "note": "reviewed source escapes bodyClasses and bodyStyles with escapeHTMLAttribute before HTML attribute insertion. the previously cited c65861cab0a3 commit changes VPN retention-policy settings, not this renderer. prior fix-date, release and production-rollout claims are not supported by that commit and are withdrawn pending separate evidence.", "classification": { "area": "semantics", "reason": "The inspected mail renderer escapes class/style attribute data before HTML insertion. This supports a data-to-markup boundary classification, not the previously recorded fix date or production rollout.", "source": "https://github.com/ProtonMail/WebClients/blob/008dfe64b21da7e0d64bc21572b5cbacb09deeab/packages/mail-renderer/helpers/getIframeHtml.ts", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-WEBCL-001/", "source_url": "https://github.com/ProtonMail/WebClients/blob/008dfe64b21da7e0d64bc21572b5cbacb09deeab/packages/mail-renderer/helpers/getIframeHtml.ts", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-PROTON-ANDROID-PASS-PASSKEY-ORIGIN-001", "repo": "protonpass/android-pass", "url": "https://github.com/protonpass/android-pass/commit/855c602584bd3ed8306a6ad5699fc770ada9baf3", "title": "fix(passkeys): validate caller origin before signing WebAuthn assertions", "status": "fixed publicly in 1.40.0 (F-Droid 1.39.2 still behind)", "reported_via": "security contact", "note": "public Proton Pass Android commit 855c602584bd adds PasskeyOriginVerifier, Digital Asset Links validation, and passkey_privileged_browsers_allowlist.json before signing WebAuthn assertions. Play/APKMirror/APKPure 1.40.0 builds contain the fix; F-Droid was still on 1.39.2 at verification time and therefore should not be treated as fixed until it updates.", "classification": { "area": "identity", "reason": "Passkey assertions require validation of the calling app or browser origin against trusted associations.", "source": "https://github.com/protonpass/android-pass/commit/855c602584bd3ed8306a6ad5699fc770ada9baf3", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-ANDROID-PASS-PASSKEY-ORIGIN-001/", "source_url": "https://github.com/protonpass/android-pass/commit/855c602584bd3ed8306a6ad5699fc770ada9baf3", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-BC-NC-TRAILINGDOT-001", "repo": "bcgit/bc-java", "url": "https://github.com/bcgit/bc-java/commit/425e4c6ec29b2cb2162dcbbfcb5adc38de40168a", "title": "normalize trailing-dot DNS names before name-constraint matching", "status": "fixed publicly", "reported_via": "security contact", "note": "A terminal DNS root-label dot could make an otherwise matching certificate DNS name miss an excluded name constraint. The Java change of 13 May 2026 normalizes one trailing dot on both the tested DNS name and constraint before exact and subtree comparison. Java 1.85 contains this check; C# 2.7.0 applies corresponding normalization in NameConstraintDns. Bouncy Castle has associated this report with CVE-2026-8763 and publicly credits 1seal alongside another researcher. The published CVE description focuses on rfc822Name and URI comparison, so this DNS fix record does not claim every DNS or C# behavior is covered by that description. This is source/version confirmation, not a new certificate-chain retest.", "credit": "1seal (Oleh Konko), listed alongside Alex Gaynor in Bouncy Castle CVE-2026-8763 credit", "classification": { "area": "identity", "reason": "DNS name-constraint comparison normalizes the root-label trailing dot before matching certificate identities.", "source": "https://github.com/bcgit/bc-java/commit/425e4c6ec29b2cb2162dcbbfcb5adc38de40168a", "reviewed": "2026-09-26" }, "patched": "Java 1.85 and C# 2.7.0", "source_reviewed": "2026-09-26", "related_sources": [ { "label": "Java 1.85: DNS normalization", "url": "https://github.com/bcgit/bc-java/blob/r1rv85/core/src/main/java/org/bouncycastle/asn1/x509/PKIXNameConstraintValidator.java" }, { "label": "C# 2.7.0: DNS normalization", "url": "https://github.com/bcgit/bc-csharp/blob/release-2.7.0/crypto/src/pkix/NameConstraintDns.cs" }, { "label": "Bouncy Castle CVE-2026-8763 and credit", "url": "https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%908763" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BC-NC-TRAILINGDOT-001/", "source_url": "https://github.com/bcgit/bc-java/commit/425e4c6ec29b2cb2162dcbbfcb5adc38de40168a", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-HUGGINGFACE-003", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-02" }, "repo": "huggingface/datasets", "url": "https://github.com/huggingface/datasets/commit/1bd0a5c087b72d705818405a7840a28d3955c08b", "title": "Don't extract bad files", "status": "fixed publicly", "reported_via": "private reporting channel", "note": "public fix commit 1bd0a5c087b7 appears to address the reported issue.", "classification": { "area": "authorization", "reason": "Archive extraction filters destination paths to prevent writes outside the extraction root.", "source": "https://github.com/huggingface/datasets/commit/1bd0a5c087b72d705818405a7840a28d3955c08b", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-HUGGINGFACE-003/", "source_url": "https://github.com/huggingface/datasets/commit/1bd0a5c087b72d705818405a7840a28d3955c08b", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-BORINGSSL-001-005", "repo": "google/boringssl", "url": "https://boringssl.googlesource.com/boringssl/+/5774eca6004ed7c7467bd644c057797ca96b65f2", "title": "crypto/x509: Fix interaction of DNS exclude constraints with wildcard DNS names.", "status": "fixed publicly", "reported_via": "Google OSS VRP / Chromium issue 487821920", "note": "excluded dNSName wildcard SAN bypass. accepted via Google OSS VRP; public BoringSSL commit 5774eca6004e landed on 2026-03-04 as CL 90167 and updates crypto/x509/v3_ncons.cc plus tests for excluded DNS constraints interacting with wildcard SANs. the commit message references Bug: 488306305, while the tracked external report id is 487821920.", "classification": { "area": "identity", "reason": "Excluded DNS constraints are not correctly applied to wildcard SANs.", "source": "https://boringssl.googlesource.com/boringssl/+/5774eca6004ed7c7467bd644c057797ca96b65f2", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BORINGSSL-001-005/", "source_url": "https://boringssl.googlesource.com/boringssl/+/5774eca6004ed7c7467bd644c057797ca96b65f2", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-BORINGSSL-001-004", "repo": "google/boringssl", "url": "https://boringssl.googlesource.com/boringssl/+/b84dc606410ec1d8e2f779de5ec6791d2951308e", "title": "crypto/x509: Tighten URI name constraints parsing and matching", "status": "fixed publicly", "reported_via": "Google OSS VRP / Chromium issue 487820706", "note": "public landed commit b84dc606410e; reviewed as CL 92687. commit message references Bug: 487820706, 502006234. fix tightens URI nameConstraints parsing and matching, rejecting userinfo@ misleading hosts, nonnumeric ports, malformed hosts, and IP/IPv6 URI hosts.", "classification": { "area": "identity", "reason": "URI authority parsing accepts malformed hosts during name-constraint validation.", "source": "https://boringssl.googlesource.com/boringssl/+/b84dc606410ec1d8e2f779de5ec6791d2951308e", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BORINGSSL-001-004/", "source_url": "https://boringssl.googlesource.com/boringssl/+/b84dc606410ec1d8e2f779de5ec6791d2951308e", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-TREZOR-THP-DOS-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/15975901acf6d909baf3062d480fe865d023b438", "title": "chore(core): improve handling of large messages", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 15975901acf6 on 2026-03-20 adds the missing `if buffer is None: return False` guard in the THP reassembly path, so oversized payload_length no longer passes as in the vulnerable pin 5ba0333910c1.", "classification": { "area": "availability", "reason": "Oversized protocol messages exhaust processing resources.", "source": "https://github.com/trezor/trezor-firmware/commit/15975901acf6d909baf3062d480fe865d023b438", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-THP-DOS-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/15975901acf6d909baf3062d480fe865d023b438", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TREZOR-SUITE-PT-001", "repo": "trezor/trezor-suite", "url": "https://github.com/trezor/trezor-suite/commit/cb76104f1068b7047591735ca691a7fed4439613", "title": "feat(suite-desktop-core): add check for path traversal", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit cb76104f1068 on 2026-02-26 canonicalizes paths inside userData through resolvePathInUserDataDir and blocks traversal from the affected metadata IPC path.", "classification": { "area": "authorization", "reason": "Untrusted path components escape the intended local directory.", "source": "https://github.com/trezor/trezor-suite/commit/cb76104f1068b7047591735ca691a7fed4439613", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-SUITE-PT-001/", "source_url": "https://github.com/trezor/trezor-suite/commit/cb76104f1068b7047591735ca691a7fed4439613", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TREZOR-SYSCALL-TRANSLATIONS-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/1811d3bb96291dfe5cbecd442719d37bce6b74c3", "title": "fix(core): use verifiers for translations syscalls", "status": "merged", "reported_via": "security contact", "note": "public fix commit 1811d3bb9629 routes translation syscalls through verified wrappers instead of raw implementations. F-TREZOR-006 is an alternate report ID for the same callsite and fix, not a separate counted finding.", "classification": { "area": "memory-safety", "reason": "Translation syscall input reaches insufficiently bounded memory.", "source": "https://github.com/trezor/trezor-firmware/commit/1811d3bb96291dfe5cbecd442719d37bce6b74c3", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-SYSCALL-TRANSLATIONS-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/1811d3bb96291dfe5cbecd442719d37bce6b74c3", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TREZOR-008", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/fb4aa180cf6fb928138bc2cc2fc8386a7d337bc0", "title": "fix(core): fix jpegdec syscall verifier", "status": "merged", "reported_via": "security contact", "note": "public fix commit fb4aa180cf6f on 2026-02-27. adds the missing jpegdec verifier-side input pointer validation.", "classification": { "area": "memory-safety", "reason": "JPEG verification accesses memory outside the intended image buffer.", "source": "https://github.com/trezor/trezor-firmware/commit/fb4aa180cf6fb928138bc2cc2fc8386a7d337bc0", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-008/", "source_url": "https://github.com/trezor/trezor-firmware/commit/fb4aa180cf6fb928138bc2cc2fc8386a7d337bc0", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TREZOR-CRYPTO-MEMZERO-002", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/48db49fa67eb4b51a30dff394e27cbea6803dbf1", "title": "fix(crypto): add missing memzero to `ed25519.c`", "status": "merged", "reported_via": "security contact", "note": "public fix commit 48db49fa67eb on 2026-02-26. clears extsk on the invalid-nonce early return path in ed25519_cosi_sign.", "classification": { "area": "confidentiality", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/48db49fa67eb4b51a30dff394e27cbea6803dbf1", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-CRYPTO-MEMZERO-002/", "source_url": "https://github.com/trezor/trezor-firmware/commit/48db49fa67eb4b51a30dff394e27cbea6803dbf1", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-CRYPTO-MEMZERO-005", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/40d4f9027d3b5f05204afb3e11d9a4dc383fa50d", "title": "fix(crypto): add missing memzero to `cardano.c`", "status": "merged", "reported_via": "security contact", "note": "public fix commit 40d4f9027d3b on 2026-02-25. clears extended private key material on hdnode_private_ckd_cardano failure paths.", "classification": { "area": "confidentiality", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/40d4f9027d3b5f05204afb3e11d9a4dc383fa50d", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-CRYPTO-MEMZERO-005/", "source_url": "https://github.com/trezor/trezor-firmware/commit/40d4f9027d3b5f05204afb3e11d9a4dc383fa50d", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-CRYPTO-MEMZERO-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/bddd38b47d920559e50aa50c82eab62a8f6510ca", "title": "fix(crypto): add missing memzero to `ecdsa.c`", "status": "merged", "reported_via": "security contact", "note": "public fix commit bddd38b47d92 clears tc_ecdsa_sign_digest secret material on error returns. F-TREZOR-CRYPTO-MEMZERO-004 is an alternate report ID for the same fix, not a separate counted finding.", "classification": { "area": "confidentiality", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/bddd38b47d920559e50aa50c82eab62a8f6510ca", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-CRYPTO-MEMZERO-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/bddd38b47d920559e50aa50c82eab62a8f6510ca", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-CRYPTO-MEMZERO-006", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/09e55d8c9cb255eaa0463a8aa58f5dca1ed17644", "title": "fix(crypto): add missing memzero to `bip32.c`", "status": "merged", "reported_via": "security contact", "note": "public fix commit 09e55d8c9cb2 on 2026-02-26. clears the NEM AES context key schedule after use.", "classification": { "area": "confidentiality", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/09e55d8c9cb255eaa0463a8aa58f5dca1ed17644", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-CRYPTO-MEMZERO-006/", "source_url": "https://github.com/trezor/trezor-firmware/commit/09e55d8c9cb255eaa0463a8aa58f5dca1ed17644", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-THP-FRAGMENT-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/d63fe0e883771a1cebb7c15ec45e2445c1821682", "title": "fix(rust/trezor-thp): check `payload_len` is not less than `CHECKSUM_LEN`", "status": "merged", "reported_via": "security contact", "note": "public fix commit d63fe0e88377 on 2026-02-25. prevents the small-payload underflow in THP fragment reassembly.", "classification": { "area": "availability", "reason": "A fragment payload shorter than its checksum can underflow checked Rust length arithmetic; rejecting it prevents parser failure, without asserting native memory corruption.", "source": "https://github.com/trezor/trezor-firmware/commit/d63fe0e883771a1cebb7c15ec45e2445c1821682", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-THP-FRAGMENT-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/d63fe0e883771a1cebb7c15ec45e2445c1821682", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TREZOR-009", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/e5c51d5ee4b33af859363afcfc104857956e8931", "title": "fix(core): fix dma2d syscall verifiers", "status": "merged", "reported_via": "security contact", "note": "public fix commit e5c51d5ee4b3 on 2026-02-27. fixes signed-overflow handling in the dma2d syscall verifier macros.", "classification": { "area": "memory-safety", "reason": "DMA2D syscalls use insufficiently bounded buffers.", "source": "https://github.com/trezor/trezor-firmware/commit/e5c51d5ee4b33af859363afcfc104857956e8931", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-009/", "source_url": "https://github.com/trezor/trezor-firmware/commit/e5c51d5ee4b33af859363afcfc104857956e8931", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TREZOR-011", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/f60f535403e6a2189a103017183224ad535b842f", "title": "fix(core): fix syscall set filter verifier", "status": "merged", "reported_via": "security contact", "note": "public fix commit f60f535403e6 on 2026-02-27. moves syslog filter validation ahead of strlen-driven access.", "classification": { "area": "memory-safety", "reason": "The filter syscall lacks the required buffer bounds.", "source": "https://github.com/trezor/trezor-firmware/commit/f60f535403e6a2189a103017183224ad535b842f", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-011/", "source_url": "https://github.com/trezor/trezor-firmware/commit/f60f535403e6a2189a103017183224ad535b842f", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TREZOR-004", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/663569c40b60d5dc62c14ae1b590ea9d54508aab", "title": "refactor: stellar confirmations", "status": "merged", "reported_via": "security contact", "note": "public fix commit 663569c40b60 on 2026-02-24. tightens Stellar payment request confirmation flow so extra operations cannot ride past the displayed confirmation set.", "classification": { "area": "semantics", "reason": "Stellar signing confirmation does not bind the displayed operation details.", "source": "https://github.com/trezor/trezor-firmware/commit/663569c40b60d5dc62c14ae1b590ea9d54508aab", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-004/", "source_url": "https://github.com/trezor/trezor-firmware/commit/663569c40b60d5dc62c14ae1b590ea9d54508aab", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-TREZOR-FW-007-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/ab9b4feaff30747a37fd9222d627e8636c78641e", "title": "fix(core): fix bug in multisig verification.", "status": "merged", "reported_via": "security contact", "note": "public fix commit ab9b4feaff30 on 2026-01-16. closes an ECDSA multisig verification loop flaw that could permit signature-acceptance bypass.", "classification": { "area": "authorization", "reason": "The corrected multisignature check enforces which signer combinations may authorize the operation.", "source": "https://github.com/trezor/trezor-firmware/commit/ab9b4feaff30747a37fd9222d627e8636c78641e", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-FW-007-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/ab9b4feaff30747a37fd9222d627e8636c78641e", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TREZOR-BIP32-001", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/26914ff4962812695a2abf49f06e268606a7a7e2", "title": "fix(crypto): Avoid caching uncacheable nodes in bip32.c", "status": "merged", "reported_via": "security contact", "note": "public fix commit 26914ff49628 on 2026-02-20. prevents the Stellar derivation path from overflowing the bounded BIP32 cache depth on Trezor One.", "classification": { "area": "confidentiality", "reason": "Derived secret key material remains in a cache beyond its intended lifetime.", "source": "https://github.com/trezor/trezor-firmware/commit/26914ff4962812695a2abf49f06e268606a7a7e2", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-BIP32-001/", "source_url": "https://github.com/trezor/trezor-firmware/commit/26914ff4962812695a2abf49f06e268606a7a7e2", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-CRYPTO-MEMZERO-003", "repo": "trezor/trezor-firmware", "url": "https://github.com/trezor/trezor-firmware/commit/477cbb365a29c23df766fd8f128cc5b73ed04bb6", "title": "fix(crypto): clean up stack in hdnode_deserialize()", "status": "merged", "reported_via": "security contact", "note": "public fix commit 477cbb365a29 on 2026-02-16. clears stack-resident key material in hdnode_deserialize(); the fix is present in public release tags including core/v2.11.0 and legacy/v1.14.1.", "classification": { "area": "confidentiality", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/477cbb365a29c23df766fd8f128cc5b73ed04bb6", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-CRYPTO-MEMZERO-003/", "source_url": "https://github.com/trezor/trezor-firmware/commit/477cbb365a29c23df766fd8f128cc5b73ed04bb6", "disclosed": null, "cwe": null, "layer": "confidentiality" }, { "finding_id": "F-TREZOR-SUITE-PM-001", "repo": "trezor/trezor-suite", "url": "https://github.com/trezor/trezor-suite/commit/c84e94b607f35eb9b5c239d9af810b744308d575", "title": "feat(connect-webextension): now uses externally_connectable api", "status": "merged", "reported_via": "security contact", "note": "public fix commit c84e94b607f3 on 2026-03-12. replaces wildcard postMessage response delivery in the connect popup flow with origin-scoped handling; the change is contained in public trezor-suite tags v26.4.1 and v26.4.2.", "classification": { "area": "authorization", "reason": "Extension connectivity permits callers outside the intended trust boundary.", "source": "https://github.com/trezor/trezor-suite/commit/c84e94b607f35eb9b5c239d9af810b744308d575", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-SUITE-PM-001/", "source_url": "https://github.com/trezor/trezor-suite/commit/c84e94b607f35eb9b5c239d9af810b744308d575", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TREZOR-SUITE-OAUTH-001", "repo": "trezor/trezor-suite", "url": "https://github.com/trezor/trezor-suite/commit/f02a8d4ceca54ac2c405a1cad8f3e00b3e748015", "title": "feat: enhance OAuth handling with zod validation and update response structure", "status": "merged", "reported_via": "security contact", "note": "public fix commit f02a8d4ceca5 on 2026-03-20. enforces state binding in the OAuth request/response flow and is contained in public trezor-suite tags v26.4.1 and v26.4.2.", "classification": { "area": "identity", "reason": "OAuth responses must remain bound to the initiating authentication request rather than supplying an unrelated identity result.", "source": "https://github.com/trezor/trezor-suite/commit/f02a8d4ceca54ac2c405a1cad8f3e00b3e748015", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-SUITE-OAUTH-001/", "source_url": "https://github.com/trezor/trezor-suite/commit/f02a8d4ceca54ac2c405a1cad8f3e00b3e748015", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-TREZOR-BLOCKBOOK-WS-READLIMIT-001", "repo": "trezor/blockbook", "url": "https://github.com/trezor/blockbook/commit/f8349fcebcdf2a9066a06245c1e68c67f3e608bd", "title": "enhancement: reject oversized websocket messages", "status": "merged", "reported_via": "security contact", "note": "public fix commit f8349fcebcdf on 2026-03-11. adds a websocket read limit to stop unbounded message-driven memory growth.", "classification": { "area": "availability", "reason": "WebSocket reads are not bounded by message size.", "source": "https://github.com/trezor/blockbook/commit/f8349fcebcdf2a9066a06245c1e68c67f3e608bd", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-BLOCKBOOK-WS-READLIMIT-001/", "source_url": "https://github.com/trezor/blockbook/commit/f8349fcebcdf2a9066a06245c1e68c67f3e608bd", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TREZOR-BLOCKBOOK-API-SENDTX-READALL-001", "repo": "trezor/blockbook", "url": "https://github.com/trezor/blockbook/commit/33b99cc7d4406be889551aa4645ea4ead7f3a004", "title": "enhancement: limit /api/sendtx body size", "status": "merged", "reported_via": "security contact", "note": "public fix commit 33b99cc7d440 on 2026-03-11. replaces unbounded request-body handling in /api/sendtx with a size limit.", "classification": { "area": "availability", "reason": "Transaction submission bodies reach unbounded reads.", "source": "https://github.com/trezor/blockbook/commit/33b99cc7d4406be889551aa4645ea4ead7f3a004", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-BLOCKBOOK-API-SENDTX-READALL-001/", "source_url": "https://github.com/trezor/blockbook/commit/33b99cc7d4406be889551aa4645ea4ead7f3a004", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TREZOR-BLOCKBOOK-001", "repo": "trezor/blockbook", "url": "https://github.com/trezor/blockbook/commit/496f8e0f3272ae604349fada565f0dff0cb78526", "title": "fix: add validation for negative ranges", "status": "merged", "reported_via": "security contact", "note": "public fix commit 496f8e0f3272 on 2026-02-25. rejects negative From/To ranges before they can reach a recoverable panic path.", "classification": { "area": "availability", "reason": "Negative range values reach invalid arithmetic/state.", "source": "https://github.com/trezor/blockbook/commit/496f8e0f3272ae604349fada565f0dff0cb78526", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-BLOCKBOOK-001/", "source_url": "https://github.com/trezor/blockbook/commit/496f8e0f3272ae604349fada565f0dff0cb78526", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001", "repo": "trezor/blockbook", "url": "https://github.com/trezor/blockbook/commit/e4fdb5ee25a58df3af52f250300cc6a6fced6d16", "title": "enhancement: avoid template.JSStr", "status": "merged", "reported_via": "security contact", "note": "public fix commit e4fdb5ee25a5 on 2026-03-16. removes the template.JSStr path in token detail rendering and adds regression coverage for XSS-safe escaping.", "classification": { "area": "semantics", "reason": "An NFT URI reaches executable markup without the required escaping.", "source": "https://github.com/trezor/blockbook/commit/e4fdb5ee25a58df3af52f250300cc6a6fced6d16", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001/", "source_url": "https://github.com/trezor/blockbook/commit/e4fdb5ee25a58df3af52f250300cc6a6fced6d16", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-ECS-FSX-001", "repo": "aws/amazon-ecs-agent", "url": "https://github.com/aws/amazon-ecs-agent/pull/4934", "title": "Use env variable to read user input when mounting FSx volumes", "status": "merged", "reported_via": "security contact", "note": "PR #4934 merged 2026-04-21, merge commit 09f274e0157d. replaces direct argv passing to powershell.exe with env-variable reads in agent/taskresource/fsxwindowsfileserver/fsxwindowsfileserver_windows.go.", "classification": { "area": "semantics", "reason": "User-controlled environment values reach shell interpretation.", "source": "https://github.com/aws/amazon-ecs-agent/pull/4934", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ECS-FSX-001/", "source_url": "https://github.com/aws/amazon-ecs-agent/pull/4934", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-AWS-EKS-PIWEBHOOK-GHA-001", "repo": "aws/amazon-eks-pod-identity-webhook", "url": "https://github.com/aws/amazon-eks-pod-identity-webhook/pull/303", "title": "pinning github action dependencies to commit sha", "status": "merged", "reported_via": "security contact", "note": "PR #303 merged 2026-04-13, merge commit 75a29dfa4349. pins .github/workflows/build.yaml third-party actions to immutable commit shas.", "classification": { "area": "provenance", "reason": "CI action dependencies are bound to commit identities instead of mutable action tags.", "source": "https://github.com/aws/amazon-eks-pod-identity-webhook/pull/303", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-EKS-PIWEBHOOK-GHA-001/", "source_url": "https://github.com/aws/amazon-eks-pod-identity-webhook/pull/303", "disclosed": null, "cwe": null, "layer": "provenance" }, { "finding_id": "F-AWS-TOUGH-006", "repo": "awslabs/tough", "url": "https://github.com/awslabs/tough/commit/0ba39c5", "title": "containment-check for targets_base_url in fetch_target", "status": "fixed publicly", "reported_via": "security contact", "note": "public code in tough 0.22.0 appears to close this read-side variant even though no separate advisory line was published for it. inferred from public diff 0ba39c5, which adds a containment-check for targets_base_url in fetch_target.", "classification": { "area": "authorization", "reason": "Target retrieval omits the targets_base_url containment check; the write-side CVE mapping is not claimed.", "source": "https://github.com/awslabs/tough/commit/0ba39c5", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-TOUGH-006/", "source_url": "https://github.com/awslabs/tough/commit/0ba39c5", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-AWS-TOUGH-DELEGATION-CHAIN-001", "repo": "awslabs/tough", "url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "title": "compound delegation chain decomposed across CVE-2026-6966 and CVE-2026-6967", "status": "fixed publicly", "reported_via": "security contact", "note": "upstream fixed and publicly released on 2026-04-24 in tough 0.22.0 / tuftool 0.15.0. the reported compound chain is publicly decomposed across GHSA-8m7c-8m39-rv4x / CVE-2026-6966 and GHSA-4v58-8p28-2rq3 / CVE-2026-6967 rather than published as a single bundled advisory.", "classification": { "area": "authorization", "reason": "The compound report concerns metadata/delegation trust checks; related receipts do not create an independent defect count.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-TOUGH-DELEGATION-CHAIN-001/", "source_url": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-AWSLC-OCSP-RESPONDER-REVOC-0", "repo": "aws/aws-lc", "url": "https://github.com/aws/aws-lc/pull/3169", "title": "Handle id-pkix-ocsp-nocheck in OCSP responder verification", "status": "fixed/documented publicly", "reported_via": "AWS Security", "note": "AWS determined the report did not present a security vulnerability to AWS-LC or s2n-tls, but released public aws-lc PR #3169 on 2026-04-30 to handle id-pkix-ocsp-nocheck in delegated OCSP responder verification. AWS also released s2n-tls PR #5859 on 2026-05-01 to document that OCSP_basic_verify() does not verify OCSP delegated responder certificates and that this is caller configuration responsibility.", "classification": { "area": "authorization", "reason": "Delegated OCSP responder authorization depends on the configured revocation policy and nocheck exception. AWS treated this as a bug/documentation update, not a security vulnerability.", "source": "https://github.com/aws/aws-lc/pull/3169", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWSLC-OCSP-RESPONDER-REVOC-0/", "source_url": "https://github.com/aws/aws-lc/pull/3169", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001", "repo": "intel/cryptography-primitives", "url": "https://github.com/intel/cryptography-primitives/commit/8c4a863575f95822df61fa12094dbcfa53fcb1b5", "title": "Fix SM2 signature forgery via missing t == 0 rejection in ippsGFpECVerifySM2", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 8c4a863575f9 landed on 2026-05-19 via #899 and shipped in Intel Cryptography Primitives Library v2.2.0, published on 2026-05-28. release notes state: fixed SM2 signature forgery vulnerability by adding missing input validation in ippsGFpECVerifySM2.", "classification": { "area": "integrity", "reason": "SM2 verification omits the required t == 0 rejection.", "source": "https://github.com/intel/cryptography-primitives/commit/8c4a863575f95822df61fa12094dbcfa53fcb1b5", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001/", "source_url": "https://github.com/intel/cryptography-primitives/commit/8c4a863575f95822df61fa12094dbcfa53fcb1b5", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-INTEL-SGX-DCAP-QCNL-OVERFLOW-001", "repo": "intel/confidential-computing.tee.dcap", "url": "https://github.com/intel/confidential-computing.tee.dcap/commit/393cbd9e3cf6454d12b99217ecb6a0f2bd268183", "title": "fix(qcnl): fix integer overflow in write_callback() on Linux", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 393cbd9e3cf6 landed on 2026-04-28 and shipped in Intel SGX/TDX DCAP 1.26, published on 2026-04-30. the Linux QCNL write_callback path changes integer arithmetic and adds a bounded buffer-growth guard.", "classification": { "area": "memory-safety", "reason": "QCNL uses checked size arithmetic before growing and copying response buffers, preventing integer overflow at the allocation boundary.", "source": "https://github.com/intel/confidential-computing.tee.dcap/commit/393cbd9e3cf6454d12b99217ecb6a0f2bd268183", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-INTEL-SGX-DCAP-QCNL-OVERFLOW-001/", "source_url": "https://github.com/intel/confidential-computing.tee.dcap/commit/393cbd9e3cf6454d12b99217ecb6a0f2bd268183", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-INTEL-IPSEC-MB-AES-CBC-LEN0-OOB-001", "repo": "intel/intel-ipsec-mb", "url": "https://github.com/intel/intel-ipsec-mb/commit/78e272a08a7cf55ec0c8e0ab4bd14a8e843dbc03", "title": "lib: [aes-cbc] fix zero-length message handling in decrypt direction", "status": "fixed publicly", "reported_via": "security contact", "note": "public fix commit 78e272a08a7c landed on 2026-04-11 and shipped in intel-ipsec-mb v2.0.2, tagged on 2026-04-21. the AES-CBC decrypt path now checks for zero-length messages before loading the IV/message buffers, avoiding the no-check API out-of-bounds read class.", "classification": { "area": "memory-safety", "reason": "The AES-CBC decrypt routine returns before accessing message data when the input length is zero.", "source": "https://github.com/intel/intel-ipsec-mb/commit/78e272a08a7cf55ec0c8e0ab4bd14a8e843dbc03", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-INTEL-IPSEC-MB-AES-CBC-LEN0-OOB-001/", "source_url": "https://github.com/intel/intel-ipsec-mb/commit/78e272a08a7cf55ec0c8e0ab4bd14a8e843dbc03", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-GHA-ARTNAME-001", "repo": "actions/download-artifact", "url": "https://github.com/actions/download-artifact/releases/tag/v8.0.0", "title": "download-artifact v8: content-type gated artifact decompression", "status": "fixed publicly (no GHSA/CVE)", "reported_via": "HackerOne", "note": "public hardening shipped in actions/download-artifact v8.0.0 on 2026-02-26: the action no longer attempts to unzip every downloaded file and checks Content-Type before extraction via PR #460. v8.0.1 on 2026-03-11 added a regression test for artifact name + content-type mismatches via PR #472. attribution linkage is inferred from topic and timing; no GHSA/CVE was published.", "classification": { "area": "unclassified", "reason": "The release contains both archive-type handling and digest enforcement. The existing report-to-change mapping is inferred, so neither area is assigned to this finding without a precise match.", "source": "https://github.com/actions/download-artifact/releases/tag/v8.0.0", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GHA-ARTNAME-001/", "source_url": "https://github.com/actions/download-artifact/releases/tag/v8.0.0", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-AMD-BOOTGEN-003", "repo": "Xilinx/bootgen", "url": "https://github.com/Xilinx/bootgen/commit/d06a738b6e997a06b251088f65ec55d4ebd6dec5", "title": "Bug fixes ported from 2026.1", "status": "fixed publicly (functional bug, no CVE)", "reported_via": "AMD PSIRT", "note": "AMD tracked SWSPLAT-9457 as a functional bug rather than a CVE. public commit d06a738b6e99 on 2026-06-01 updates the Versal verify path so unauthenticated images fail closed when neither the image header table nor any partition has authentication metadata, closing the bootgen -arch versal -verify false-positive behavior reported in F-AMD-BOOTGEN-003.", "classification": { "area": "integrity", "reason": "Boot image verification now rejects an image with no authentication certificate rather than reporting successful authentication.", "source": "https://github.com/Xilinx/bootgen/commit/d06a738b6e997a06b251088f65ec55d4ebd6dec5", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AMD-BOOTGEN-003/", "source_url": "https://github.com/Xilinx/bootgen/commit/d06a738b6e997a06b251088f65ec55d4ebd6dec5", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-TON-006-001", "repo": "ton-blockchain/ton", "url": "https://github.com/ton-blockchain/ton/pull/2191", "title": "arm RLDP receiver timeouts and validate FEC before receiver allocation", "status": "fixed in public source; rollout not reverified", "reported_via": "TON contest / security process", "note": "PR #2191 merged on 2026-03-09 as d9bc8b9520964817a704949cd6eb50527f595559. The diff arms the receiver alarm in start_up and validates fec_type before receiver creation in RldpIn::process_message_part. These match the reported callsites. F-TON-007-001 describes the same receiver-state defect and is an alternate ID, not a separate counted finding. This source-level mapping does not establish public vendor attribution or a deployed release.", "classification": { "area": "availability", "reason": "Incomplete or malformed RLDP transfers could retain receiver state without an armed expiry alarm; the matched patch schedules expiry and validates FEC before allocation.", "source": "https://github.com/ton-blockchain/ton/pull/2191", "reviewed": "2026-09-23" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TON-006-001/", "source_url": "https://github.com/ton-blockchain/ton/pull/2191", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TON-009-001", "repo": "ton-blockchain/ton", "url": "https://github.com/ton-blockchain/ton/pull/2208", "title": "node/security-relevant fixes", "status": "fixed publicly (mapped by date and fix area)", "reported_via": "TON contest / security process", "note": "PR #2208 merged on 2026-03-17 with merge commit 3abee30359120c51bfbbd05a589ae31ffa7d453d. the public PR includes node/security-relevant fixes including error handling and memory allocation fixes; the merge commit remains present in current testnet and master.", "classification": { "area": "unclassified", "reason": "The linked PR contains several node and database fixes; no exact public finding-to-change mapping identifies a primary security area.", "source": "https://github.com/ton-blockchain/ton/pull/2208", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TON-009-001/", "source_url": "https://github.com/ton-blockchain/ton/pull/2208", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-TON-010-001", "repo": "ton-blockchain/ton", "url": "https://github.com/ton-blockchain/ton/pull/2211", "title": "Fix empty collated data / Removing null-consensus", "status": "fixed publicly (mapped by date and fix area)", "reported_via": "TON contest / security process", "note": "two strong public fix candidates landed on 2026-03-19: PR #2211 commit 4d49b714ecfbc2e1bf23e75b9fadc75399122fb0 (Fix empty collated data) and PR #2209 commit 39731934d4fbbf6dce4d84509afed424a44c853c (Removing null-consensus). both commits remain present in current testnet and master; mapping is by reported fix date and consensus-area change, not public F-TON disclosure.", "classification": { "area": "unclassified", "reason": "The record names two different candidate fixes. The precise reported defect remains unresolved, so consensus-related project context is not used as a substitute.", "source": "https://github.com/ton-blockchain/ton/pull/2211", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TON-010-001/", "source_url": "https://github.com/ton-blockchain/ton/pull/2211", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-LIBRESSL-NC-WILDCARD-001", "repo": "libressl/openbsd", "url": "https://github.com/libressl/openbsd/commit/cf3eec32e7a6acbaecd14871fb75ad34fb76c3e7", "title": "fix SAN dNSName constraints matching", "status": "fixed publicly (GHSA metadata unconfirmed)", "reported_via": "private security contact", "note": "public OpenBSD/LibreSSL commit cf3eec32e7a6 on 2026-04-13 fixes SAN dNSName name-constraints matching by replacing substring/suffix matching with exact DNSName constraint semantics and adding regression coverage. LibreSSL 4.3.0/4.3.1 include the fix; 4.3.1 release notes explicitly mention the SAN dNSName constraints fix and 4.3.2 stable includes it. GHSA-h674-q4g3-3g47 was not publicly accessible at verification time, so this is tracked as a public upstream fixed mapping rather than confirmed GHSA/CVE metadata.", "classification": { "area": "identity", "reason": "DNS name constraints require exact or label-boundary matches instead of unrestricted suffix matches.", "source": "https://github.com/libressl/openbsd/commit/cf3eec32e7a6acbaecd14871fb75ad34fb76c3e7", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LIBRESSL-NC-WILDCARD-001/", "source_url": "https://github.com/libressl/openbsd/commit/cf3eec32e7a6acbaecd14871fb75ad34fb76c3e7", "disclosed": null, "cwe": null, "layer": "identity" }, { "finding_id": "F-SIGANDROID-INTENT-001", "repo": "signalapp/Signal-Android", "url": "https://github.com/signalapp/Signal-Android/commit/fecb30a86eaa984e9495a486555150a9c4bc9b08", "title": "mark ApkUpdatePackageInstallerReceiver non-exported", "status": "fixed publicly (high confidence mapping)", "reported_via": "private security contact", "note": "maps to GHSL-2026-102: Intent redirection through the website APK updater. public commit fecb30a86eaa on Signal-Android changes ApkUpdatePackageInstallerReceiver from android:exported=\"true\" to false; the commit is included in v8.4.2 and the official latest channel was at 8.15.3 at verification time.", "classification": { "area": "authorization", "reason": "The website APK installer receiver is no longer exported, restricting access from other Android applications.", "source": "https://github.com/signalapp/Signal-Android/commit/fecb30a86eaa984e9495a486555150a9c4bc9b08", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIGANDROID-INTENT-001/", "source_url": "https://github.com/signalapp/Signal-Android/commit/fecb30a86eaa984e9495a486555150a9c4bc9b08", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-SIGNAL-SERVER-PREKEY-001", "repo": "signalapp/Signal-Server", "url": "https://github.com/signalapp/Signal-Server/commit/b7d455ed114069ddff0e21b3ddfd7eaf6cc3994d", "title": "validate pre-key key-id ranges", "status": "likely fixed publicly (conditional mapping)", "reported_via": "private security contact", "note": "public Signal-Server commits b7d455ed1140, b441fde2130, and fb84066f09df validate pre-key key-id ranges, enforce positive signed 32-bit ids, and align gRPC prekey rate-limit keys; these commits are present in tag v20260618.2.0. mapped to F-SIGNAL-SERVER-PREKEY-001 only if the private report concerned prekey key_id ranges / invalid ids / gRPC prekey limiter behavior; if it concerned depletion or last-resort semantics, an exact public fix was not observed.", "classification": { "area": "unclassified", "reason": "The key-ID range patch is public, but the record also allows a different prekey-depletion interpretation. The exact finding-to-patch mapping must be resolved first.", "source": "https://github.com/signalapp/Signal-Server/commit/b7d455ed114069ddff0e21b3ddfd7eaf6cc3994d", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-SIGNAL-SERVER-PREKEY-001/", "source_url": "https://github.com/signalapp/Signal-Server/commit/b7d455ed114069ddff0e21b3ddfd7eaf6cc3994d", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-ENVOY-001-003", "repo": "envoyproxy/envoy", "url": "https://github.com/envoyproxy/envoy/issues/44032", "title": "uhv: use-after-free read in sanitizeHeadersWithUnderscores with duplicate underscore headers", "status": "fixed publicly via issue closure", "reported_via": "public GitHub issue", "note": "public issue #44032 was opened by @1seal and describes a UHV use-after-free read in HeaderValidator::sanitizeHeadersWithUnderscores() when duplicate underscore headers are dropped via non-owning string_view references. the issue is closed and cross-references #44086; tracked as fixed based on the public issue status, without a separate CVE/GHSA or release claim.", "classification": { "area": "memory-safety", "reason": "Duplicate underscore headers trigger a use-after-free read during sanitization.", "source": "https://github.com/envoyproxy/envoy/issues/44032", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ENVOY-001-003/", "source_url": "https://github.com/envoyproxy/envoy/issues/44032", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-LEDGER-LIVE-DESKTOP-CUSTOMDAPPURL-001", "repo": "LedgerHQ/ledger-live", "url": "https://github.com/LedgerHQ/ledger-live/releases/tag/%40ledgerhq%2Flive-desktop%402.135.2", "title": "fix(wallet-api): add domain validation for customDappUrl", "status": "fixed publicly", "reported_via": "security contact", "note": "Ledger Live Desktop @ledgerhq/live-desktop@2.135.2, released on 2026-01-09, includes PR #13602 / commit 48d299c adding domain validation for customDappUrl. release notes state customDappUrl is only applied when it matches the original manifest URL domain, preventing cross-domain URL manipulation.", "classification": { "area": "authorization", "reason": "A custom dapp URL crosses the manifest's intended domain boundary.", "source": "https://github.com/LedgerHQ/ledger-live/releases/tag/%40ledgerhq%2Flive-desktop%402.135.2", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-LIVE-DESKTOP-CUSTOMDAPPURL-001/", "source_url": "https://github.com/LedgerHQ/ledger-live/releases/tag/%40ledgerhq%2Flive-desktop%402.135.2", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-PROTON-DRIVE-SDK-001", "repo": "ProtonDriveApps/sdk", "url": "https://github.com/ProtonDriveApps/sdk/commit/451c1bf", "title": "Avoid content key packet verification fallback on publicly shared nodes", "status": "likely fixed publicly", "reported_via": "security contact", "note": "public Proton Drive SDK commit 451c1bf disables content-key packet verification fallback for publicly shared nodes by setting allowContentKeyPacketFallbackVerification=false in SharingPublicNodesCryptoService. mapped as a strong public fix match; no CVE/GHSA claim is made for this record.", "classification": { "area": "integrity", "reason": "Publicly shared nodes no longer fall back to a content-key verification path that cannot load the owner address keys.", "source": "https://github.com/ProtonDriveApps/sdk/commit/451c1bf", "reviewed": "2026-09-21" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROTON-DRIVE-SDK-001/", "source_url": "https://github.com/ProtonDriveApps/sdk/commit/451c1bf", "disclosed": null, "cwe": null, "layer": "integrity" }, { "finding_id": "F-NOTARYPROJECT-KYVERNO-001", "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "repo": "kyverno/kyverno", "url": "https://github.com/kyverno/kyverno/pull/16208", "title": "verifyImages(required): enforce matching images after non-matching images", "status": "fixed in Kyverno v1.18.2 and v1.19.0", "reported_via": "security contact", "note": "PR #16208 skips non-matching images instead of ending validation, preserving required verification for matching images in multi-container workloads. merged on 2026-06-01 (5cb31ab); backported to 1.18 via PR #16218 (a8c7016). fixed releases: v1.19.0 and v1.18.2.", "classification": { "area": "authorization", "reason": "Required image verification must apply to every matching image before admission; an earlier non-matching image must not bypass that authorization policy.", "source": "https://github.com/kyverno/kyverno/pull/16208", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NOTARYPROJECT-KYVERNO-001/", "source_url": "https://github.com/kyverno/kyverno/pull/16208", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TRIVY-TF-FILE-001", "repo": "aquasecurity/trivy", "url": "https://github.com/aquasecurity/trivy/commit/9d91b888cf63023e9c09b64259a4c1cea8dfe993", "title": "sandbox Terraform filesystem functions", "status": "fixed in Trivy v0.71.0+", "reported_via": "security contact", "note": "revalidated with a minimal Terraform file(\"../secret.txt\") PoC through mapfs.WithUnderlyingRoot: Trivy v0.70.0 reads POC_SECRET from outside the scan root, while v0.71.0 and v0.71.2 block traversal with no file exists at ../secret.txt. upstream fix commit 9d91b888cf63 shipped in v0.71.0 and makes Terraform filesystem functions use a sandboxed FS without access to the underlying OS root. CVE-2026-104994 was published on 2026-10-02 for this Terraform filesystem-function issue.", "classification": { "area": "authorization", "reason": "Terraform file functions read outside the scan root.", "source": "https://github.com/aquasecurity/trivy/commit/9d91b888cf63023e9c09b64259a4c1cea8dfe993", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRIVY-TF-FILE-001/", "source_url": "https://github.com/aquasecurity/trivy/commit/9d91b888cf63023e9c09b64259a4c1cea8dfe993", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-NIMIQ-SCANQR-JSREDIRECT-001", "repo": "nimiq/wallet", "url": "https://github.com/nimiq/wallet/commit/df954de", "title": "ScanQrModal: fix domain check for cashlinks", "status": "fixed publicly in wallet v3.2.3", "reported_via": "security contact", "note": "public wallet commit df954de fixes the domain check for cashlinks in ScanQrModal; Nimiq wallet release v3.2.3 contains the fix.", "classification": { "area": "authorization", "reason": "A scanned cashlink bypasses the intended navigation-domain check.", "source": "https://github.com/nimiq/wallet/commit/df954de", "reviewed": "2026-09-24" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NIMIQ-SCANQR-JSREDIRECT-001/", "source_url": "https://github.com/nimiq/wallet/commit/df954de", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-ESO-LABELBYPASS-001", "repo": "external-secrets/external-secrets", "number": 5901, "title": "fix: webhook initialization order", "url": "https://github.com/external-secrets/external-secrets/pull/5901", "status": "merged", "disclosed": "2026-02-02", "note": "Public PR #5901 fixes webhook generator initialization order. The linked GHSA-q7hv-xx6h-q2x8 was published on 2026-10-06 and credits @1seal as a reporter; the PR and advisory are separate evidence for one finding.", "classification": { "area": "authorization", "reason": "The recorded webhook initialization-order fix concerns bypassing the intended validation policy.", "source": "https://github.com/external-secrets/external-secrets/pull/5901", "reviewed": "2026-09-24" }, "related_sources": [ { "label": "Published vendor advisory", "url": "https://github.com/external-secrets/external-secrets/security/advisories/GHSA-q7hv-xx6h-q2x8" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-ESO-LABELBYPASS-001/", "source_url": "https://github.com/external-secrets/external-secrets/pull/5901", "cwe": null, "layer": "authorization" }, { "repo": "flutter/flutter", "url": "https://github.com/flutter/flutter/commit/79ab0aabbc8452461f115d18731138d403cad987", "title": "APNG frame buffer size: checked multiplication before allocation", "status": "fixed publicly", "patched": "Public fix committed 2026-04-23; first containing release not established", "source_reviewed": "2026-10-07", "credit": "Public fix author: Jason Simmons. Public 1seal credit and a causal link to our report are not established.", "note": "The public patch checks overflow in row-byte and pixel-buffer multiplication before allocation. It matches the frame-size calculation in the earlier report, separate from F-FLUTTER-APNG-001 (short fdAT chunks). No remote code execution claim or new product execution is made here.", "classification": { "area": "memory-safety", "reason": "Unchecked multiplication can produce an incorrect APNG frame buffer size.", "source": "https://github.com/flutter/flutter/commit/79ab0aabbc8452461f115d18731138d403cad987", "reviewed": "2026-10-07" }, "finding_id": "F-FLUTTER-APNG-002", "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-FLUTTER-APNG-002/", "source_url": "https://github.com/flutter/flutter/commit/79ab0aabbc8452461f115d18731138d403cad987", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "repo": "theopolis/uefi-firmware-parser", "url": "https://github.com/theopolis/uefi-firmware-parser/commit/86d283452c8deceb4e854fd16433748c74638a5c", "title": "Firmware extraction: sanitize partition, module and volume path components", "status": "fixed publicly", "patched": "Public fix committed 2026-06-04; first containing release not established", "source_reviewed": "2026-10-07", "credit": "Public fix author: Teddy Reed. Public 1seal credit and a causal link to our report are not established.", "note": "One shared public fix covers both report IDs: ME partition/manifest dump paths and firmware volume dump paths now use sanitized components. The patch also adds path containment tests. This records the matching extraction-path correction, not two independent fixes. Tiano decompression CVEs do not apply to this record; symlink-safe extraction is not claimed.", "classification": { "area": "authorization", "reason": "Firmware-controlled path components can escape the intended extraction directory.", "source": "https://github.com/theopolis/uefi-firmware-parser/commit/86d283452c8deceb4e854fd16433748c74638a5c", "reviewed": "2026-10-07" }, "finding_ids": [ "F-UEFI-FIRMWARE-PATH-TRAVERSAL-001", "F-UEFI-FIRMWARE-PATH-TRAVERSAL-002" ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-UEFI-FIRMWARE-PATH-TRAVERSAL-001/", "source_url": "https://github.com/theopolis/uefi-firmware-parser/commit/86d283452c8deceb4e854fd16433748c74638a5c", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "prometheus/prometheus", "url": "https://github.com/prometheus/prometheus/pull/18539", "title": "Scaleway service discovery: honor follow_redirects in the configured HTTP client", "status": "fixed publicly", "patched": "Verified in Prometheus 3.12.0; first fixed release across all branches not established", "source_reviewed": "2026-10-07", "credit": "Public fix author: roidelapluie. Public 1seal credit and a causal link to our report are not established.", "note": "Merged 2026-04-21. NewClientFromConfig replaces the direct RoundTripper so the configured redirect policy is used. This matches the earlier report about follow_redirects being ignored. The retained maintainer response treated it as a configuration correction, not a security vulnerability. It is not a claim that every redirect-related credential exposure is fixed.", "classification": { "area": "semantics", "reason": "The HTTP client must preserve the explicitly configured redirect behavior.", "source": "https://github.com/prometheus/prometheus/pull/18539", "reviewed": "2026-10-07" }, "finding_id": "F-PROMETHEUS-SCALEWAY-SD-001", "related_sources": [ { "label": "Verified fixed 3.12.0 source", "url": "https://github.com/prometheus/prometheus/blob/v3.12.0/discovery/scaleway/scaleway.go" }, { "label": "Exact client-construction patch", "url": "https://github.com/prometheus/prometheus/commit/ddca8ee45af9ca7d7c092442dc57eb8c56290850" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-PROMETHEUS-SCALEWAY-SD-001/", "source_url": "https://github.com/prometheus/prometheus/pull/18539", "disclosed": null, "cwe": null, "layer": "semantics" }, { "repo": "bazelbuild/bazel", "url": "https://github.com/bazelbuild/bazel/commit/a6836fe459ae01cf5426982e08615e05c94e8c67", "title": "Starlark debug server: bind to loopback by default", "status": "fixed publicly", "patched": "Public main-branch fix committed 2026-07-21; first containing release not established", "source_reviewed": "2026-10-07", "credit": "Public fix author: twerth. Public 1seal credit and a causal link to our report are not established.", "note": "The patch adds experimental_skylark_debug_server_address with default 127.0.0.1 instead of a wildcard listener. Debugging must be explicitly enabled and is disabled by default; a user can still configure a network-facing address. This records the matching default-bind correction, not unauthenticated access to ordinary Bazel builds.", "classification": { "area": "authorization", "reason": "An explicitly enabled debugger should not accept network connections beyond its intended local scope by default.", "source": "https://github.com/bazelbuild/bazel/commit/a6836fe459ae01cf5426982e08615e05c94e8c67", "reviewed": "2026-10-07" }, "finding_id": "F-BAZEL-001-004", "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-BAZEL-001-004/", "source_url": "https://github.com/bazelbuild/bazel/commit/a6836fe459ae01cf5426982e08615e05c94e8c67", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "aws/aws-network-policy-agent", "url": "https://github.com/aws/aws-network-policy-agent/pull/563", "title": "Network policy agent: distinguish pod-name and namespace keys", "status": "fixed publicly", "patched": "AWS network policy agent v1.3.7 contains PR #563", "source_reviewed": "2026-10-07", "credit": "Public fix author: parlakisik. Public 1seal credit and a causal link to our report are not established.", "note": "Merged 2026-05-21. The patch separates pod name and namespace in GetPodNamespacedName so different objects do not share an ambiguous concatenated key. The earlier local test called the real helper with device operations substituted; it did not demonstrate traffic on a running cluster. This is a matching key correction, not a general network-policy bypass claim. CVE-2026-86831 concerns a different helper and patch and is not assigned to this record.", "classification": { "area": "authorization", "reason": "Ambiguous pod/namespace keys can associate distinct objects with the same policy-tracking state.", "source": "https://github.com/aws/aws-network-policy-agent/pull/563", "reviewed": "2026-10-07" }, "finding_id": "F-AWS-NPA-001", "related_sources": [ { "label": "Exact key-separation patch", "url": "https://github.com/aws/aws-network-policy-agent/commit/bc504a4db01d649babb842b08c72f07a5e56c4e2" }, { "label": "v1.3.7 release including PR #563", "url": "https://github.com/aws/aws-network-policy-agent/releases/tag/v1.3.7" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-AWS-NPA-001/", "source_url": "https://github.com/aws/aws-network-policy-agent/pull/563", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "aws/aws-network-policy-agent", "url": "https://github.com/aws/aws-network-policy-agent/pull/562", "title": "Network policy agent: return errors from eBPF map updates", "status": "fixed publicly", "patched": "AWS network policy agent v1.3.7 contains PR #562", "source_reviewed": "2026-10-07", "credit": "Public fix author: parlakisik. Public 1seal credit and a causal link to our report are not established.", "note": "Merged 2026-05-21. The patch returns joined errors from policy and pod-state map updates instead of hiding failed writes and adds caller-facing regression tests. This matches the reported error-propagation defect and is separate from PR #563. The earlier reduced model did not demonstrate traffic blocking after a failure. Complete network protection after partial update failure is not established by this record; no separate CVE is assigned.", "classification": { "area": "authorization", "reason": "A failed policy-map update must return an error so its caller does not treat incomplete enforcement as success.", "source": "https://github.com/aws/aws-network-policy-agent/pull/562", "reviewed": "2026-10-07" }, "finding_id": "F-NPA-FAILOPEN-001", "related_sources": [ { "label": "Exact error-propagation patch", "url": "https://github.com/aws/aws-network-policy-agent/commit/8f364925251d3bed1b9bf89715a44c4fcb2614ee" }, { "label": "v1.3.7 release including PR #562", "url": "https://github.com/aws/aws-network-policy-agent/releases/tag/v1.3.7" } ], "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-NPA-FAILOPEN-001/", "source_url": "https://github.com/aws/aws-network-policy-agent/pull/562", "disclosed": null, "cwe": null, "layer": "authorization" }, { "repo": "decred/dcrlnd", "url": "https://github.com/decred/dcrlnd/commit/d11b48570880053b9348481c90370aba4b76bec9", "title": "Filtered chain view: unlock the filter mutex on transaction parse failure", "status": "fixed publicly", "patched": "Public fix committed 2026-05-04; first containing release not established", "source_reviewed": "2026-10-07", "credit": "Public fix author: Jamie Holdstock. Public 1seal credit and a causal link to our report are not established.", "note": "The patch releases filterMtx before returning from the failed transaction decode in onBlockConnected, matching the error path in the earlier report. Reaching this path requires malformed data from the configured dcrd backend. Arbitrary remote triggering, inevitable loss of funds and an officially accepted security report are not claimed.", "classification": { "area": "availability", "reason": "An error return with the filter mutex still held can stall later chain-view operations.", "source": "https://github.com/decred/dcrlnd/commit/d11b48570880053b9348481c90370aba4b76bec9", "reviewed": "2026-10-07" }, "finding_id": "F-DCRLND-CHAINVIEW-DEADLOCK-001", "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-DCRLND-CHAINVIEW-DEADLOCK-001/", "source_url": "https://github.com/decred/dcrlnd/commit/d11b48570880053b9348481c90370aba4b76bec9", "disclosed": null, "cwe": null, "layer": "availability" }, { "finding_id": "F-TRUSTWALLET-CBOR-001", "repo": "trustwallet/wallet-core", "number": 4707, "url": "https://github.com/trustwallet/wallet-core/pull/4707", "title": "CBOR length handling", "status": "merged", "credit": "Reported by 1seal (Oleh Konko).", "note": "1seal (Oleh Konko) reported a CBOR length-handling issue in Trust Wallet wallet-core. The issue was addressed in the public code change: https://github.com/trustwallet/wallet-core/pull/4707.", "source_reviewed": "2026-10-07", "classification": { "area": "memory-safety", "reason": "CBOR length handling.", "source": "https://github.com/trustwallet/wallet-core/pull/4707", "reviewed": "2026-10-07" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRUSTWALLET-CBOR-001/", "source_url": "https://github.com/trustwallet/wallet-core/pull/4707", "disclosed": null, "cwe": null, "layer": "memory-safety" }, { "finding_id": "F-TRUSTWALLET-PUBKEY-001", "repo": "trustwallet/wallet-core", "number": 4693, "url": "https://github.com/trustwallet/wallet-core/pull/4693", "title": "ECDSA message-length validation", "status": "merged", "credit": "Reported by 1seal (Oleh Konko).", "note": "1seal (Oleh Konko) reported a message-length validation issue in ECDSA verification in Trust Wallet wallet-core. The issue was addressed in the public code change: https://github.com/trustwallet/wallet-core/pull/4693.", "source_reviewed": "2026-10-07", "classification": { "area": "integrity", "reason": "ECDSA message-length validation.", "source": "https://github.com/trustwallet/wallet-core/pull/4693", "reviewed": "2026-10-07" }, "record_type": "reported", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-TRUSTWALLET-PUBKEY-001/", "source_url": "https://github.com/trustwallet/wallet-core/pull/4693", "disclosed": null, "cwe": null, "layer": "integrity" } ], "historical_public_fixes": [ { "finding_id": "F-LEDGER-YEARN-RECIPIENT-HIDDEN-001", "repo": "LedgerHQ/app-plugin-yearn", "url": "https://github.com/LedgerHQ/app-plugin-yearn/commit/1ba98ff", "title": "Updated to use the latest plugin SDK", "status": "fixed before report", "note": "public repo history shows the issue was already closed before the 2026-02-18 report. commit 1ba98ff, landed on 2023-10-17, already contains the Recipient screen in public code.", "classification": { "area": "semantics", "reason": "Recipient details are absent from the signing confirmation; the fix predates this report.", "source": "https://github.com/LedgerHQ/app-plugin-yearn/commit/1ba98ff", "reviewed": "2026-09-24" }, "record_type": "historical", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-YEARN-RECIPIENT-HIDDEN-001/", "source_url": "https://github.com/LedgerHQ/app-plugin-yearn/commit/1ba98ff", "disclosed": null, "cwe": null, "layer": "semantics" }, { "finding_id": "F-LEDGER-LIVE-WSBRIDGE-001", "repo": "LedgerHQ/ledger-live", "url": "https://github.com/LedgerHQ/ledger-live/commit/28fd570", "title": "Farewell 'Device Bridge' in LLD (#2635)", "status": "feature removed publicly", "note": "this appears closed in the current public product as a removal/sunset rather than a direct security fix. public ledger-live commit 28fd570 removed websocketBridge.js on 2023-03-14, and dd642a4 followed on 2023-03-16 to fully sunset internal commands. caveat: the original finding referenced the older LedgerHQ/ledger-live-desktop path.", "classification": { "area": "unclassified", "reason": "The cited feature removal does not establish a specific defect mechanism for this report.", "source": "https://github.com/LedgerHQ/ledger-live/commit/28fd570", "reviewed": "2026-09-24" }, "record_type": "historical", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-LEDGER-LIVE-WSBRIDGE-001/", "source_url": "https://github.com/LedgerHQ/ledger-live/commit/28fd570", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "finding_id": "F-TGDESKTOP-CLIPBOARD-001", "repo": "telegramdesktop/tdesktop", "url": "https://github.com/telegramdesktop/tdesktop/commit/d349a28d7645", "title": "Track interactions in webview for clipboard access", "status": "fixed before report", "note": "public commit d349a28d7645 on 2026-02-28 gates clipboard reads on a recent real webview interaction within kClipboardReadTimeout. the fix predates the submitted Telegram bundle and is tracked as a parallel public closure rather than report-driven remediation.", "classification": { "area": "authorization", "reason": "Clipboard reads need a recent genuine user interaction; the fix predates this report.", "source": "https://github.com/telegramdesktop/tdesktop/commit/d349a28d7645", "reviewed": "2026-09-24" }, "record_type": "historical", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TGDESKTOP-CLIPBOARD-001/", "source_url": "https://github.com/telegramdesktop/tdesktop/commit/d349a28d7645", "disclosed": null, "cwe": null, "layer": "authorization" }, { "finding_id": "F-TELEGRAM-VECOVF-001", "repo": "tdlib/td", "url": "https://github.com/tdlib/td/commit/9722906f9a0bfc673eccd576050f299579e95602", "title": "TDLib public change; vector-overflow fix mapping unconfirmed", "status": "fix mapping unconfirmed", "note": "review on 2026-09-21 found that the cited commit changes PhotoSizeSource fatal logging, not vector-length validation. the earlier claim that this commit fixed the reported vector overflow before submission is withdrawn; this row is retained as an uncounted historical record pending a correct source.", "classification": { "area": "unclassified", "reason": "The cited commit changes fatal logging for PhotoSizeSource; it does not implement the claimed vector-length check. The previous fix mapping is unsupported by that source.", "source": "https://github.com/tdlib/td/commit/9722906f9a0bfc673eccd576050f299579e95602", "reviewed": "2026-09-24" }, "record_type": "historical", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-TELEGRAM-VECOVF-001/", "source_url": "https://github.com/tdlib/td/commit/9722906f9a0bfc673eccd576050f299579e95602", "disclosed": null, "cwe": null, "layer": "unclassified" } ], "code_hardening_contribs": [ { "repo": "chainguard-dev/malcontent", "number": 1354, "url": "https://github.com/chainguard-dev/malcontent/pull/1354", "finding_id": "F-MALCONTENT-006", "title": "fix: register defers immediately in scan.go", "status": "merged", "reported_via": "security contact", "classification": { "area": "availability", "reason": "Scanner resources and file descriptors are not reliably released.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/chainguard-dev/malcontent/pull/1354", "author": "egibs", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "hardening", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-006/", "source_url": "https://github.com/chainguard-dev/malcontent/pull/1354", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "chainguard-dev/malcontent", "number": 1355, "url": "https://github.com/chainguard-dev/malcontent/pull/1355", "finding_id": "F-MALCONTENT-008", "title": "fix treewide: register more defers immediately", "status": "merged", "reported_via": "security contact", "classification": { "area": "availability", "reason": "Deferred cleanup retains archive resources longer than intended.", "source": "https://github.com/chainguard-dev/malcontent/pull/1355", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/chainguard-dev/malcontent/pull/1355", "author": "stevebeattie", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "hardening", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-008/", "source_url": "https://github.com/chainguard-dev/malcontent/pull/1355", "disclosed": null, "cwe": null, "layer": "availability" }, { "repo": "chainguard-dev/malcontent", "number": 1356, "url": "https://github.com/chainguard-dev/malcontent/pull/1356", "finding_id": "F-MALCONTENT-007", "title": "fix: abstract out cpio operations to helper function", "status": "merged", "reported_via": "security contact", "classification": { "area": "unclassified", "reason": "The public archive-helper refactor does not establish a specific security property or defect. It remains an engineering contribution, not an assigned vulnerability area.", "source": "https://github.com/chainguard-dev/malcontent/pull/1356", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/chainguard-dev/malcontent/pull/1356", "author": "stevebeattie", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "hardening", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-MALCONTENT-007/", "source_url": "https://github.com/chainguard-dev/malcontent/pull/1356", "disclosed": null, "cwe": null, "layer": "unclassified" } ], "testing_contribs": [ { "repo": "openssl/fuzz-corpora", "number": 32, "url": "https://github.com/openssl/fuzz-corpora/pull/32", "finding_id": "F-OPENSSL-ASN1-001", "title": "asn1parse: add small ber/der edge-case seeds", "status": "applied upstream", "note": "closed without github-merge; maintainer applied with tweaked commit message.", "classification": { "area": "unclassified", "reason": "The public ASN.1 fuzz-corpus contribution covers parser edge cases but does not establish a specific affected security property. Testing is not promoted to a confirmed defect.", "source": "https://github.com/openssl/fuzz-corpora/pull/32", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/openssl/fuzz-corpora/pull/32", "author": "1seal", "state": "closed", "merged": false, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "testing", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-OPENSSL-ASN1-001/", "source_url": "https://github.com/openssl/fuzz-corpora/pull/32", "disclosed": null, "cwe": null, "layer": "unclassified" }, { "repo": "google/go-attestation", "number": 496, "url": "https://github.com/google/go-attestation/pull/496", "finding_id": "F-GO-ATTESTATION-004", "title": "test: add ECDSA activation regression coverage", "status": "merged", "note": "merged on 2026-05-19 as commit 33eb399; adds activation_test.go coverage that CheckAKParameters rejects ECC AK public-key parse failures and invalid ECDSA signatures after the verifyECDSASignature fail-open fix.", "classification": { "area": "identity", "reason": "Regression tests reject invalid ECDSA activation signatures and malformed attestation public keys, protecting attestation identity verification. This is test coverage, not an additional vulnerability.", "source": "https://github.com/google/go-attestation/pull/496", "reviewed": "2026-09-24" }, "pr_evidence": { "source_url": "https://github.com/google/go-attestation/pull/496", "author": "1seal", "state": "closed", "merged": true, "observed_at": "2026-09-24", "observation_basis": "Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed." }, "record_type": "testing", "counted": true, "canonical_url": "https://1seal.org/research/findings/F-GO-ATTESTATION-004/", "source_url": "https://github.com/google/go-attestation/pull/496", "disclosed": null, "cwe": null, "layer": "identity" } ], "finding_classifications": { "F-NPM-CLI-001": { "category": "access-control", "reason": "A textual path prefix is mistaken for package ownership, allowing replacement of another package's executable link.", "source": "https://github.com/npm/bin-links/pull/173", "reviewed": "2026-09-26" }, "F-DOCUSAURUS-DEPLOY-ARGINJECT-001": { "category": "injection", "reason": "Branch-name data is interpolated into a command string instead of remaining one argument.", "source": "https://github.com/facebook/docusaurus/commit/23e6a41db15f17251fe22e93537ebede354e20c0", "reviewed": "2026-09-26" }, "F-PROXYGEN-BINARYHTTP-001": { "category": "input-handling", "reason": "Incorrect length accounting shifts the boundary between a Binary HTTP header section and the following data.", "source": "https://github.com/facebook/proxygen/commit/479eb5574195764e80e6cedebef669f6baa85083", "reviewed": "2026-09-26" }, "F-WHATSAPP-WARAFT-001": { "category": "path-traversal", "reason": "A peer-supplied snapshot path crosses the receiving transport's filesystem boundary.", "source": "https://github.com/WhatsApp/waraft/commit/32ae20329488d110b4303ef8ca1022ce02c43fe4", "reviewed": "2026-09-26" }, "F-PROTON-VPN-ANDROID-GLANCE-001": { "category": "access-control", "reason": "Externally supplied activity intents can enter a path intended only for internal widget actions.", "source": "https://github.com/ProtonVPN/android-app/commit/114faaaf270647f01e1614731b93241c07366f98", "reviewed": "2026-09-26" }, "F-PROTON-IOS-AUTH-001": { "category": "access-control", "reason": "An incoming OTP URL reaches import processing before the local authentication gate is satisfied.", "source": "https://github.com/protonpass/ios-authenticator/commit/2dfa196a08011687ca596cbd96a1bf1729ff1251", "reviewed": "2026-09-26" }, "F-PROTON-DRIVE-DEEPLINK-001": { "category": "access-control", "reason": "A second upload entry point bypasses URI validation already used for external inputs.", "source": "https://github.com/ProtonDriveApps/android-drive/commit/74b5c034d1070fdcc378027dd4e1e2cdcd818fb8", "reviewed": "2026-09-26" }, "F-PROTON-WALLET-FLUTTER-001": { "category": "secret-handling", "reason": "Mnemonic material is copied from recovery/import processing into diagnostic logs.", "source": "https://github.com/ProtonWallet/flutter-app/commit/e40a7e56c0ab0f3e36d057282da5342097d67040", "reviewed": "2026-09-26" }, "F-BC-NC-MULTIAT-001": { "category": "verification", "reason": "Splitting a quoted mailbox at the first at-sign compares the wrong domain against certificate name constraints.", "source": "https://github.com/bcgit/bc-java/commit/a535c77060258d8ad5cd2aaadd723894aee3b695", "reviewed": "2026-09-26" }, "F-WHISPER-001-002": { "category": "memory-safety", "reason": "A model-controlled dimension count indexes beyond the fixed-size dimension array in the model loaders.", "source": "https://github.com/ggml-org/whisper.cpp/commit/df1547b6fe362556e48fd21f386c6eee85b971fe", "reviewed": "2026-09-26" }, "F-NEO-NOTARY-001": { "category": "input-handling", "reason": "Fee accounting uses a shared payer boundary instead of the individual notary depositor and accumulated obligations.", "source": "https://github.com/neo-project/neo/commit/abbc3a259e93459e7b4b9174b62a3189410fbd44", "reviewed": "2026-09-26" }, "F-LIBSIGNAL-MAC-LOG-001": { "category": "secret-handling", "reason": "Authentication-tag values from message verification are unnecessarily exposed through a diagnostic log.", "source": "https://github.com/signalapp/libsignal/commit/0dc09edf868c7fe21a78ced960a621debbd95513", "reviewed": "2026-09-26" }, "F-WIREGUARD-001-001": { "category": "path-traversal", "reason": "A tunnel-name-to-path conversion lacks a local name-validation boundary; the upstream fix adds it defensively.", "source": "https://github.com/WireGuard/wireguard-windows/commit/b1b1bfee5dd393332976f2f200151838a3e242ef", "reviewed": "2026-09-26" }, "F-ACROSS-009-001": { "category": "access-control", "reason": "Nested tryMulticall bypasses a forbidden-selector policy.", "source": "https://github.com/across-protocol/contracts/pull/1405", "reviewed": "2026-09-24" }, "F-AMD-BOOTGEN-003": { "category": "verification", "reason": "The verify path reports success without the required authentication certificate.", "source": "https://github.com/Xilinx/bootgen/commit/d06a738b6e997a06b251088f65ec55d4ebd6dec5", "reviewed": "2026-09-24" }, "F-APISIX-CLS-HTTP-001": { "category": "secret-handling", "reason": "The change defaults log transport to HTTPS instead of plaintext.", "source": "https://github.com/apache/apisix/commit/f609ea332af7333acebc04bd20c2878233285129", "reviewed": "2026-09-24" }, "F-APISIX-OIDC-TLS-001": { "category": "verification", "reason": "OIDC transport does not enable certificate verification by default.", "source": "https://github.com/apache/apisix/commit/dd42b19feb15d12b0f6dbfbfdae6f4f2207d0f2c", "reviewed": "2026-09-24" }, "F-APKO-001": { "category": "path-traversal", "reason": "Filesystem operations escape the directory-backed root.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-5g94-c2wx-8pxw", "reviewed": "2026-09-24" }, "F-APKO-002": { "category": "input-handling", "reason": "An unexpected JWKS key type triggers a panic.", "source": "https://github.com/advisories/GHSA-m7hm-vm4x-28jf", "reviewed": "2026-09-24" }, "F-APKO-003": { "category": "resource-limits", "reason": "Archive splitting permits unbounded resource consumption.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-6p9p-q6wh-9j89", "reviewed": "2026-09-24" }, "F-APKO-007": { "category": "resource-limits", "reason": "APK expansion lacks an effective output-size bound.", "source": "https://github.com/chainguard-dev/apko/security/advisories/GHSA-f4w5-5xv9-85f6", "reviewed": "2026-09-24" }, "F-APKO-CHECKSUM-001": { "category": "verification", "reason": "Package checksums are not enforced on the affected path.", "source": "https://github.com/advisories/GHSA-hcwr-pq9g-rq3m", "reviewed": "2026-09-24" }, "F-APKO-SYMLINK-001": { "category": "path-traversal", "reason": "Symlink traversal defeats filesystem containment.", "source": "https://github.com/advisories/GHSA-qq3r-w4hj-gjp6", "reviewed": "2026-09-24" }, "F-ARGO-ARTIFACT-001": { "category": "general-hardening", "reason": "The public change documents artifact security requirements rather than establishing a specific code defect here.", "source": "https://github.com/argoproj/argo-workflows/pull/15466", "reviewed": "2026-09-24" }, "F-ARGOPROJ-001": { "category": "resource-limits", "reason": "Request body consumption lacks an effective size limit.", "source": "https://github.com/argoproj/argo-workflows/commit/7dc19c8a3306a5085ae92ceab56726933fb1aa9e", "reviewed": "2026-09-24" }, "F-AUTHZED-SPICEDB-001": { "category": "input-handling", "reason": "Untrusted cursor parsing reaches a MustParse panic.", "source": "https://github.com/authzed/spicedb/security/advisories/GHSA-vhvq-fv9f-wh4q", "reviewed": "2026-09-24" }, "F-AWS-CLI-BOTOCORE-S3SSRF-001": { "category": "ssrf", "reason": "A server-supplied region influences an outbound endpoint.", "source": "https://github.com/boto/botocore/commit/86d458dd4b8aeeb02a5ab198194b4e61569663ce", "reviewed": "2026-09-24" }, "F-AWS-CW-AGENT-GHA-001": { "category": "general-hardening", "reason": "Workflow dependencies are pinned to immutable revisions.", "source": "https://github.com/aws/amazon-cloudwatch-agent/pull/2071", "reviewed": "2026-09-24" }, "F-AWS-EKS-PIWEBHOOK-GHA-001": { "category": "general-hardening", "reason": "Workflow dependencies are pinned to immutable revisions.", "source": "https://github.com/aws/amazon-eks-pod-identity-webhook/pull/303", "reviewed": "2026-09-24" }, "F-AWS-ENCRYPTION-SDK-PYTHON-001": { "category": "verification", "reason": "Cached key material bypasses a required key-commitment check.", "source": "https://github.com/aws/aws-encryption-sdk-python/security/advisories/GHSA-v638-38fc-rhfv", "reviewed": "2026-09-24" }, "F-AWS-EVENT-STREAM-001": { "category": "memory-safety", "reason": "An unbounded header-name length leads to an out-of-bounds write.", "source": "https://github.com/awslabs/aws-c-event-stream/security/advisories/GHSA-xvjw-fjq5-68hf", "reviewed": "2026-09-24" }, "F-AWS-LC-NAMECONSTRAINTS-001": { "category": "verification", "reason": "Wildcard common names bypass name-constraint enforcement.", "source": "https://github.com/aws/aws-lc/commit/2aa522465f69d6c8576983c4f61c1fc60c5d0411", "reviewed": "2026-09-24" }, "F-AWS-LC-NAMECONSTRAINTS-002": { "category": "verification", "reason": "Unicode common names are skipped by name-constraint enforcement.", "source": "https://github.com/aws/aws-lc/security/advisories/GHSA-3jrg-j22w-mpmc", "reviewed": "2026-09-24" }, "F-AWS-ROLESANYWHERE-GHA-001": { "category": "general-hardening", "reason": "Workflow dependencies are pinned to immutable revisions.", "source": "https://github.com/aws/rolesanywhere-credential-helper/commit/b4207adb8856ed81710f92f7692440122ea12765", "reviewed": "2026-09-24" }, "F-AWS-S2N-TLS-IP-CN-001": { "category": "verification", "reason": "An IP literal is accepted through common-name hostname fallback.", "source": "https://github.com/aws/s2n-tls/pull/5804", "reviewed": "2026-09-24" }, "F-AWS-SDK-GO-V2-ES-001": { "category": "input-handling", "reason": "An unknown eventstream header type triggers an unrecoverable panic.", "source": "https://github.com/aws/aws-sdk-go-v2/security/advisories/GHSA-xmrv-pmrh-hhx2", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-001": { "category": "verification", "reason": "Metadata signature thresholds are not correctly enforced.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-002": { "category": "verification", "reason": "Metadata validation fails to enforce the required trust checks.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-003": { "category": "verification", "reason": "Metadata validation fails to enforce the required trust checks.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-004": { "category": "verification", "reason": "Metadata validation fails to enforce the required trust checks.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-005": { "category": "verification", "reason": "Unvalidated metadata can poison the trusted local cache.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-4v58-8p28-2rq3", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-006": { "category": "path-traversal", "reason": "Target retrieval omits the targets_base_url containment check; the write-side CVE mapping is not claimed.", "source": "https://github.com/awslabs/tough/commit/0ba39c5", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-007": { "category": "path-traversal", "reason": "Target writing escapes the intended local directory.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-008": { "category": "path-traversal", "reason": "Target writing escapes the intended local directory.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-009": { "category": "path-traversal", "reason": "Target writing escapes the intended local directory.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-v57p-gppj-p9vg", "reviewed": "2026-09-24" }, "F-AWS-TOUGH-DELEGATION-CHAIN-001": { "category": "verification", "reason": "The compound report concerns metadata/delegation trust checks; related receipts do not create an independent defect count.", "source": "https://github.com/awslabs/tough/security/advisories/GHSA-8m7c-8m39-rv4x", "reviewed": "2026-09-24" }, "F-AWS-XRAY-DAEMON-GHA-001": { "category": "general-hardening", "reason": "Workflow dependencies are pinned to immutable revisions.", "source": "https://github.com/aws/aws-xray-daemon/commit/946763a48ab5a9be3a161598642355bc9d9e3459", "reviewed": "2026-09-24" }, "F-AWS-XRAY-DAEMON-GHA-002": { "category": "general-hardening", "reason": "Workflow dependency pins are corrected.", "source": "https://github.com/aws/aws-xray-daemon/commit/4abe89b868badc59b85288d6bf74763d8ca46577", "reviewed": "2026-09-24" }, "F-AWSLC-OCSP-RESPONDER-REVOC-0": { "category": "verification", "reason": "The report concerns delegated responder revocation policy; AWS treated it as a bug/documentation update, not a security vulnerability.", "source": "https://github.com/aws/aws-lc/pull/3169", "reviewed": "2026-09-24" }, "F-AWSRUST-CACHE-001": { "category": "access-control", "reason": "Credential cache files are created with overly broad local permissions.", "source": "https://github.com/smithy-lang/smithy-rs/pull/4584", "reviewed": "2026-09-24" }, "F-BC-NC-TRAILINGDOT-001": { "category": "verification", "reason": "Trailing-dot DNS normalization is inconsistent with name-constraint enforcement.", "source": "https://github.com/bcgit/bc-java/commit/425e4c6ec29b2cb2162dcbbfcb5adc38de40168a", "reviewed": "2026-09-26" }, "F-BORINGSSL-001-004": { "category": "verification", "reason": "URI authority parsing accepts malformed hosts during name-constraint validation.", "source": "https://boringssl.googlesource.com/boringssl/+/b84dc606410ec1d8e2f779de5ec6791d2951308e", "reviewed": "2026-09-24" }, "F-BORINGSSL-001-005": { "category": "verification", "reason": "Excluded DNS constraints are not correctly applied to wildcard SANs.", "source": "https://boringssl.googlesource.com/boringssl/+/5774eca6004ed7c7467bd644c057797ca96b65f2", "reviewed": "2026-09-24" }, "F-BOULDER-009": { "category": "general-hardening", "reason": "The recorded change avoids mutation of shared HTTP transport defaults; a narrower defect is not established here.", "source": "https://github.com/letsencrypt/boulder/pull/8641", "reviewed": "2026-09-24" }, "F-BUILDAH-SYMLINK-001": { "category": "path-traversal", "reason": "Tar extraction permits writes outside the intended directory.", "source": "https://github.com/podman-container-tools/buildah/security/advisories/GHSA-3528-5p26-cf44", "reviewed": "2026-09-24" }, "F-BUILDKIT-001-001": { "category": "path-traversal", "reason": "ContainerID traversal escapes the executor root.", "source": "https://github.com/moby/buildkit/security/advisories/GHSA-4c29-8rgm-jvjj", "reviewed": "2026-09-24" }, "F-CADDY-ACME-POLICY-001": { "category": "access-control", "reason": "The warning concerns an unset certificate issuance permission policy, not a newly confirmed exploit.", "source": "https://github.com/caddyserver/caddy/pull/7469", "reviewed": "2026-09-24" }, "F-CADDY-ADMIN-LOAD-001": { "category": "access-control", "reason": "Cross-origin requests reach the administrative configuration interface.", "source": "https://github.com/caddyserver/caddy/security/advisories/GHSA-879p-475x-rqh2", "reviewed": "2026-09-24" }, "F-CADDY-CERTMAGIC-OCSP-001": { "category": "verification", "reason": "Delegated OCSP responders require explicit signing authorization.", "source": "https://github.com/caddyserver/certmagic/pull/378", "reviewed": "2026-09-24" }, "F-CADDY-FILESERVER-HIDE-CASE-001": { "category": "access-control", "reason": "The documented hide-rule boundary depends on filesystem case behavior.", "source": "https://github.com/caddyserver/website/pull/529", "reviewed": "2026-09-24" }, "F-CEDAR-PST-ERRORCONSTRAINT-001": { "category": "access-control", "reason": "Serialization widens an invalid policy constraint to match all actions.", "source": "https://github.com/cedar-policy/cedar/pull/2246", "reviewed": "2026-09-24" }, "F-CERTMGR-DNS-001": { "category": "input-handling", "reason": "Malformed DNS response fields reach a panic.", "source": "https://github.com/cert-manager/cert-manager/security/advisories/GHSA-gx3x-vq4p-mhhv", "reviewed": "2026-09-24" }, "F-CHAINGUARD-FORKS-KANIKO-AG5-001": { "category": "path-traversal", "reason": "Archive extraction crosses the intended build filesystem boundary.", "source": "https://github.com/chainguard-forks/kaniko/security/advisories/GHSA-6rxq-q92g-4rmf", "reviewed": "2026-09-24" }, "F-CILIUM-001-002": { "category": "secret-handling", "reason": "The contribution warns about unprotected Relay transport; it does not enable TLS by default.", "source": "https://github.com/cilium/cilium/pull/44772", "reviewed": "2026-09-24" }, "F-CONFLUENTIC-SCHEMA-REGISTRY-REST-BODY-NOCAP-001": { "category": "resource-limits", "reason": "REST body processing requires a configured request-size limit.", "source": "https://github.com/confluentinc/schema-registry/commit/bd56596", "reviewed": "2026-09-24" }, "F-CONTAINERD-DESCURLS-001": { "category": "ssrf", "reason": "Descriptor URLs can receive sensitive headers intended for a different destination.", "source": "https://github.com/containerd/containerd/pull/12889", "reviewed": "2026-09-24" }, "F-COSIGN-001-003": { "category": "verification", "reason": "Certificate validation does not enforce the issuing CA validity boundary.", "source": "https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm", "reviewed": "2026-09-24" }, "F-COSIGN-003": { "category": "input-handling", "reason": "Malformed replacement operations reach an unchecked type assertion.", "source": "https://github.com/sigstore/cosign/pull/4653", "reviewed": "2026-09-24" }, "F-COSIGN-004": { "category": "input-handling", "reason": "A nil transparency-log entry reaches an unchecked access.", "source": "https://github.com/sigstore/cosign/pull/4649", "reviewed": "2026-09-24" }, "F-COSIGN-005": { "category": "input-handling", "reason": "An unexpected body type reaches an unchecked string assertion.", "source": "https://github.com/sigstore/cosign/pull/4652", "reviewed": "2026-09-24" }, "F-COSIGN-006": { "category": "input-handling", "reason": "Malformed attestation input reaches an unchecked type assertion.", "source": "https://github.com/sigstore/cosign/pull/4651", "reviewed": "2026-09-24" }, "F-CTGO-S2A-001": { "category": "resource-limits", "reason": "An HTTP request body is not bounded before processing.", "source": "https://github.com/google/certificate-transparency-go/pull/1754", "reviewed": "2026-09-24" }, "F-CTGO-TIMEOUT-001": { "category": "resource-limits", "reason": "Missing timeouts leave HTTP operations unbounded.", "source": "https://github.com/google/certificate-transparency-go/pull/1755", "reviewed": "2026-09-24" }, "F-DCRWALLET-001": { "category": "access-control", "reason": "Malformed authenticate RPC input can avoid the invalid-credentials decision.", "source": "https://github.com/decred/dcrwallet/pull/2617", "reviewed": "2026-09-24" }, "F-DECRED-DCRD-RPC-LIMITED-ONLY-001": { "category": "access-control", "reason": "Limited RPC credentials cross the intended method-permission boundary.", "source": "https://github.com/decred/dcrd/commit/2d6b77049f1c529fb9c40099098c64a863825e7b", "reviewed": "2026-09-24" }, "F-DENO-001-001": { "category": "access-control", "reason": "Network deny rules are not applied to resolved IP addresses.", "source": "https://github.com/denoland/deno/pull/33203", "reviewed": "2026-09-24" }, "F-DIST-PROXY-SSRF-001": { "category": "ssrf", "reason": "A registry-controlled realm redirects credential-bearing token requests.", "source": "https://github.com/distribution/distribution/security/advisories/GHSA-3p65-76g6-3w7r", "reviewed": "2026-09-24" }, "F-DIST-REDIS-REVIVAL-001": { "category": "access-control", "reason": "Stale cached access state revives access that should no longer be granted.", "source": "https://github.com/distribution/distribution/security/advisories/GHSA-f2g3-hh2r-cwgc", "reviewed": "2026-09-24" }, "F-ECS-FSX-001": { "category": "injection", "reason": "User-controlled environment values reach shell interpretation.", "source": "https://github.com/aws/amazon-ecs-agent/pull/4934", "reviewed": "2026-09-24" }, "F-EKSPIA-GHA-001": { "category": "general-hardening", "reason": "Workflow dependencies are pinned to immutable revisions.", "source": "https://github.com/aws/eks-pod-identity-agent/commit/cdb0dd49a89fec783d7fec365ea0449222ba416e", "reviewed": "2026-09-24" }, "F-EKSPIA-GHA-002": { "category": "general-hardening", "reason": "Workflow dependency hardening is recorded without a distinct exploit mechanism.", "source": "https://github.com/aws/eks-pod-identity-agent/commit/dcae60b05e537055fa11315d8305f018e40dbf2e", "reviewed": "2026-09-24" }, "F-ELEMENTX-IOS-001": { "category": "access-control", "reason": "An unchecked call-link origin is loaded with application WebView privileges.", "source": "https://github.com/element-hq/element-x-ios/security/advisories/GHSA-54w7-rw44-49m7", "reviewed": "2026-09-24" }, "F-ENVOY-001-002": { "category": "input-handling", "reason": "A valid 255-octet DNS name violates an incorrect runtime precondition.", "source": "https://github.com/envoyproxy/envoy/security/advisories/GHSA-j6g2-wf95-q66q", "reviewed": "2026-09-24" }, "F-ENVOY-001-003": { "category": "memory-safety", "reason": "Duplicate underscore headers trigger a use-after-free read during sanitization.", "source": "https://github.com/envoyproxy/envoy/issues/44032", "reviewed": "2026-09-24" }, "F-ESO-LABELBYPASS-001": { "category": "access-control", "reason": "The recorded webhook initialization-order fix concerns bypassing the intended validation policy.", "source": "https://github.com/external-secrets/external-secrets/pull/5901", "reviewed": "2026-09-24" }, "F-FIREFOX-AVIF-MP4PARSE-OFFSET-001": { "category": "input-handling", "reason": "Offset narrowing fails to preserve the required nonnegative range; exploitability is not asserted.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020538", "reviewed": "2026-09-24" }, "F-FIREFOX-IPC-PUSH-012": { "category": "access-control", "reason": "The removed IPC path concerns principal/scope authorization; removal is not proof of exploitation.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2022681", "reviewed": "2026-09-24" }, "F-FLUTTER-APNG-001": { "category": "memory-safety", "reason": "A short APNG fdAT chunk reaches an out-of-bounds access.", "source": "https://github.com/flutter/flutter/pull/186700", "reviewed": "2026-09-24" }, "F-FREEIPA-389DS-001": { "category": "resource-limits", "reason": "LDAP control processing permits excessive CPU and memory use.", "source": "https://access.redhat.com/security/cve/cve-2026-9064", "reviewed": "2026-09-24" }, "F-GHA-ARTNAME-001": { "category": "needs-detail", "reason": "The public artifact-hardening cluster does not establish an exact report-to-fix mapping.", "source": "https://github.com/actions/download-artifact/releases/tag/v8.0.0", "reviewed": "2026-09-24" }, "F-GK-EXT-001": { "category": "resource-limits", "reason": "An external operation lacks an effective timeout.", "source": "https://github.com/open-policy-agent/gatekeeper/pull/4351", "reviewed": "2026-09-24" }, "F-GNUPG-001-002": { "category": "path-traversal", "reason": "gpgtar symlink traversal escapes the selected output directory.", "source": "https://github.com/sailfishos-mirror/gnupg/commit/7a2692fe5e580ae3bbb2a47abc4baaf1af65aa88", "reviewed": "2026-09-24" }, "F-GNUTLS-HOSTNAME-001": { "category": "verification", "reason": "URI or SRV SAN entries incorrectly permit common-name fallback.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "F-GNUTLS-NAMECONSTRAINTS-001": { "category": "verification", "reason": "Case-sensitive DNS comparison bypasses certificate name constraints.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "F-GNUTLS-OCSP-001": { "category": "verification", "reason": "Multi-entry OCSP processing can miss a revoked status.", "source": "https://gitlab.com/gnutls/gnutls/-/merge_requests/2102", "reviewed": "2026-09-24" }, "F-GO-ATTESTATION-001": { "category": "input-handling", "reason": "Malformed EFI list lengths underflow before the required lower-bound check.", "source": "https://github.com/google/go-attestation/commit/becfd074e9ceded0e5e4cc56f3eb25d43e930c00", "reviewed": "2026-09-24" }, "F-GO-ATTESTATION-004": { "category": "verification", "reason": "Regression coverage checks ECDSA key extraction and invalid-signature rejection; it is not an additional vulnerability.", "source": "https://github.com/google/go-attestation/pull/496", "reviewed": "2026-09-24" }, "F-GO-X509-WILDCARD-CASE-001": { "category": "verification", "reason": "Wildcard case handling bypasses certificate name constraints; downstream receipts share this ID.", "source": "https://github.com/containerd/containerd/pull/13189", "reviewed": "2026-09-24" }, "F-HARBOR-REALM-001": { "category": "ssrf", "reason": "The documented realm-trust issue concerns credential-bearing outbound destinations.", "source": "https://github.com/goharbor/website/pull/706", "reviewed": "2026-09-24" }, "F-HEADSCALE-001-001": { "category": "resource-limits", "reason": "Machine-map request bodies are not bounded before processing.", "source": "https://github.com/juanfont/headscale/commit/4d427cfe2af6bd9bb71d1e2abcc987d2b0906e20", "reviewed": "2026-09-24" }, "F-HEADSCALE-001-002": { "category": "resource-limits", "reason": "Verification request bodies are not bounded before processing.", "source": "https://github.com/juanfont/headscale/commit/42b8c779a02e5bfad6cef5967a7f2e2a107a2707", "reviewed": "2026-09-24" }, "F-HELM-UNTAR-ROOT-COLLAPSE-001": { "category": "path-traversal", "reason": "Archive root handling defeats extraction containment.", "source": "https://github.com/helm/helm/releases/tag/v4.1.4", "reviewed": "2026-09-24" }, "F-HUGGINGFACE-003": { "category": "path-traversal", "reason": "Archive extraction escapes the intended filesystem root.", "source": "https://github.com/huggingface/datasets/commit/1bd0a5c087b72d705818405a7840a28d3955c08b", "reviewed": "2026-09-24" }, "F-INTEL-IPP-CRYPTO-SM2-VERIFY-T0-FORGERY-001": { "category": "verification", "reason": "SM2 verification omits the required t == 0 rejection.", "source": "https://github.com/intel/cryptography-primitives/commit/8c4a863575f95822df61fa12094dbcfa53fcb1b5", "reviewed": "2026-09-24" }, "F-INTEL-IPSEC-MB-AES-CBC-LEN0-OOB-001": { "category": "memory-safety", "reason": "Zero-length AES-CBC input reaches out-of-bounds processing.", "source": "https://github.com/intel/intel-ipsec-mb/commit/78e272a08a7cf55ec0c8e0ab4bd14a8e843dbc03", "reviewed": "2026-09-24" }, "F-INTEL-SGX-DCAP-QCNL-OVERFLOW-001": { "category": "memory-safety", "reason": "QCNL buffer growth uses overflowing integer arithmetic.", "source": "https://github.com/intel/confidential-computing.tee.dcap/commit/393cbd9e3cf6454d12b99217ecb6a0f2bd268183", "reviewed": "2026-09-24" }, "F-INTOTO-CROSS-IMPL-001": { "category": "verification", "reason": "Cross-implementation negation semantics weaken policy verification.", "source": "https://github.com/in-toto/in-toto-golang/security/advisories/GHSA-pmwq-pjrm-6p5r", "reviewed": "2026-09-24" }, "F-ISTIO-001": { "category": "access-control", "reason": "XDS debug endpoints require authentication.", "source": "https://github.com/istio/istio/pull/59054", "reviewed": "2026-09-24" }, "F-ISTIO-JWKS-001": { "category": "ssrf", "reason": "JWKS fetching permits an untrusted outbound destination.", "source": "https://github.com/istio/istio/security/advisories/GHSA-fgw5-hp8f-xfhc", "reviewed": "2026-09-24" }, "F-ISTIO-JWKS-002": { "category": "verification", "reason": "A hardcoded fallback key changes the signature-verification trust decision.", "source": "https://github.com/istio/istio/security/advisories/GHSA-v75c-crr9-733c", "reviewed": "2026-09-24" }, "F-ISTIO-XDS-DEBUG-001": { "category": "access-control", "reason": "Debug access must be scoped to the caller's namespace.", "source": "https://github.com/istio/istio/pull/59970", "reviewed": "2026-09-24" }, "F-ISTIO-XDSDEBUG-002": { "category": "access-control", "reason": "Debug access crosses namespace boundaries.", "source": "https://github.com/istio/istio/security/advisories/GHSA-974c-2wxh-g4ww", "reviewed": "2026-09-24" }, "F-KARPENTER-TOOLCHAIN-001": { "category": "general-hardening", "reason": "An unpinned latest toolchain dependency is removed.", "source": "https://github.com/aws/karpenter-provider-aws/pull/9038", "reviewed": "2026-09-24" }, "F-KEYCLOAK-SAML-001": { "category": "verification", "reason": "Encrypted SAML assertion handling bypasses required validation.", "source": "https://github.com/keycloak/keycloak/security/advisories/GHSA-794g-x443-36f7", "reviewed": "2026-09-24" }, "F-KYVERNO-APICALL-001": { "category": "ssrf", "reason": "A policy-controlled API destination receives ambient credentials.", "source": "https://github.com/kyverno/kyverno/security/advisories/GHSA-q93q-v844-jrqp", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-BIP32-001": { "category": "memory-safety", "reason": "A BIP32 buffer move has an off-by-one boundary error.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/0586ab2f940c290dcaba89ca307b85589831aa2e", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-MERKLE-001": { "category": "verification", "reason": "Merkle preimage validation fails to bind the signing-path data.", "source": "/research/advisories/1SEAL-2026-005", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-MUSIG-001": { "category": "secret-handling", "reason": "MuSig secret buffers are not cleared on the affected path.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/78bac7790772b6f0adefecc76be4c4d514ce5fa7", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-NEGRC-002": { "category": "memory-safety", "reason": "A negative return value becomes an unsigned buffer length.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/70dcdf0cac8be7a35468a0c83fe0e5cbedcecbc6", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-OBO-001": { "category": "memory-safety", "reason": "Capacity handling has an off-by-one buffer error.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/e04898b32a7eed5c4fa2d4611181113b63ae9644", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-PREIMAGE-001": { "category": "memory-safety", "reason": "Preimage writes require an explicit destination-buffer bound.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/7f8e57be74052a9b31c240d9a9e7b56a6f655aee", "reviewed": "2026-09-24" }, "F-LEDGER-BTC-USTREAM-001": { "category": "input-handling", "reason": "Empty stream chunks violate parser assumptions.", "source": "https://github.com/LedgerHQ/app-bitcoin/commit/8ff2b62094af27f41d46b84ff2f49e94d8b43dc2", "reviewed": "2026-09-24" }, "F-LEDGER-ETH-EIP712-CALLDATA-001": { "category": "display-binding", "reason": "An ineffective calldata filter breaks the intended clear-signing display boundary.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/d61639c", "reviewed": "2026-09-24" }, "F-LEDGER-ETH-GCS-CLEANUP-DOUBLEFREE-001": { "category": "memory-safety", "reason": "Clear-signing cleanup can free the same allocation twice.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/601c828", "reviewed": "2026-09-24" }, "F-LEDGER-ETH-GCS-COLLECTION-OOBWRITE-001": { "category": "memory-safety", "reason": "Generic clear-signing collection parsing writes outside its buffer.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/2fb636d904f4528eaa4f84ef89f05179f0b4999c", "reviewed": "2026-09-24" }, "F-LEDGER-ETH-GCS-U16-OFFSET-SPLICE-001": { "category": "display-binding", "reason": "A truncated calldata offset changes which content is displayed before signing.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/2a96dc8d0b3a7111ef38cdb0a1365da46fae5a07", "reviewed": "2026-09-24" }, "F-LEDGER-ETH-USTREAM-001": { "category": "display-binding", "reason": "Stream offsets disconnect displayed transaction content from parsed bytes.", "source": "https://github.com/LedgerHQ/app-ethereum/commit/48f77149ad40d5b81777466de9becb3dc241152f", "reviewed": "2026-09-24" }, "F-LEDGER-LIVE-DESKTOP-CUSTOMDAPPURL-001": { "category": "access-control", "reason": "A custom dapp URL crosses the manifest's intended domain boundary.", "source": "https://github.com/LedgerHQ/ledger-live/releases/tag/%40ledgerhq%2Flive-desktop%402.135.2", "reviewed": "2026-09-24" }, "F-LEDGER-LIVE-WSBRIDGE-001": { "category": "needs-detail", "reason": "The cited feature removal does not establish a specific defect mechanism for this report.", "source": "https://github.com/LedgerHQ/ledger-live/commit/28fd570", "reviewed": "2026-09-24" }, "F-LEDGER-YEARN-RECIPIENT-HIDDEN-001": { "category": "display-binding", "reason": "Recipient details are absent from the signing confirmation; the fix predates this report.", "source": "https://github.com/LedgerHQ/app-plugin-yearn/commit/1ba98ff", "reviewed": "2026-09-24" }, "F-LIBRESSL-NC-WILDCARD-001": { "category": "verification", "reason": "Substring/suffix matching weakens DNS name-constraint enforcement.", "source": "https://github.com/libressl/openbsd/commit/cf3eec32e7a6acbaecd14871fb75ad34fb76c3e7", "reviewed": "2026-09-24" }, "F-LIBSIGNAL-JNI-DESTROY-UB-001": { "category": "memory-safety", "reason": "JNI destruction violates mutable-reference lifetime/aliasing requirements.", "source": "https://github.com/signalapp/libsignal/commit/895b079448396c1d0ba051de4f2b5b5fea64d5ef", "reviewed": "2026-09-24" }, "F-MALCONTENT-001": { "category": "path-traversal", "reason": "Archive extraction escapes its intended directory.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-923j-vrcg-hxwh", "reviewed": "2026-09-24" }, "F-MALCONTENT-003": { "category": "secret-handling", "reason": "The advisory describes exposure of registry credentials during OCI scanning.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-9m43-p3cx-w8j5", "reviewed": "2026-09-24" }, "F-MALCONTENT-006": { "category": "resource-limits", "reason": "Scanner resources and file descriptors are not reliably released.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-54p8-x2m9-c593", "reviewed": "2026-09-24" }, "F-MALCONTENT-007": { "category": "general-hardening", "reason": "The public change refactors archive helpers without establishing a distinct defect mechanism here.", "source": "https://github.com/chainguard-dev/malcontent/pull/1356", "reviewed": "2026-09-24" }, "F-MALCONTENT-008": { "category": "resource-limits", "reason": "Deferred cleanup retains archive resources longer than intended.", "source": "https://github.com/chainguard-dev/malcontent/pull/1355", "reviewed": "2026-09-24" }, "F-MALCONTENT-010": { "category": "verification", "reason": "Archive extraction failure can omit content from the security scan.", "source": "https://github.com/chainguard-dev/malcontent/security/advisories/GHSA-945p-3jhm-6rcp", "reviewed": "2026-09-24" }, "F-MELANGE-001": { "category": "injection", "reason": "Working-directory handling reaches command execution.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-vqqr-rmpc-hhg2", "reviewed": "2026-09-24" }, "F-MELANGE-003": { "category": "resource-limits", "reason": "Downloads can exhaust disk space without an effective limit.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-7rp8-r62p-q6wc", "reviewed": "2026-09-24" }, "F-MELANGE-004": { "category": "path-traversal", "reason": "Package metadata influences an unchecked filesystem path.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j", "reviewed": "2026-09-24" }, "F-MELANGE-005": { "category": "path-traversal", "reason": "QEMU runner path handling permits an escape.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-qxx2-7h4c-83f4", "reviewed": "2026-09-24" }, "F-MELANGE-006": { "category": "path-traversal", "reason": "License file resolution reads outside the intended root.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-2w4f-9fgg-q2v9", "reviewed": "2026-09-24" }, "F-MELANGE-007": { "category": "injection", "reason": "License metadata can reach host command interpretation.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-rf4g-89h5-crcr", "reviewed": "2026-09-24" }, "F-MELANGE-008": { "category": "path-traversal", "reason": "External pipeline resolution escapes the intended directory.", "source": "https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9", "reviewed": "2026-09-24" }, "F-MOBY-001-001": { "category": "access-control", "reason": "An oversized request body bypasses the authorization plugin decision.", "source": "https://github.com/moby/moby/commit/7a767b27fd1238c89a5cc926c39e27d3bcf58e35", "reviewed": "2026-09-24" }, "F-MOZILLA-FIREFOX-001": { "category": "memory-safety", "reason": "The recorded WebGPU hardening addresses size arithmetic; reachable exploitation remains unconfirmed.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2018451", "reviewed": "2026-09-24" }, "F-MOZILLA-SOPS-002": { "category": "path-traversal", "reason": "A non-local exec-file filename escapes temporary-file cleanup.", "source": "https://github.com/getsops/sops/security/advisories/GHSA-x4cm-pcq4-39j4", "reviewed": "2026-09-24" }, "F-MOZILLA-SOPS-004": { "category": "ssrf", "reason": "Untrusted Vault metadata chooses the destination receiving a local token.", "source": "https://github.com/getsops/sops/security/advisories/GHSA-jgf3-f6rg-8x3h", "reviewed": "2026-09-24" }, "F-NGINX-HTTP-REQ-002": { "category": "input-handling", "reason": "Bare line feeds lead to inconsistent HTTP request framing.", "source": "https://github.com/nginx/nginx/commit/f405ef11fde6ed749318a844c010ce97483a8f98", "reviewed": "2026-09-24" }, "F-NIMIQ-BLOCKINCLUSIONPROOF-INTERLINK-HOPS-001": { "category": "verification", "reason": "An empty or incomplete inclusion path can satisfy proof verification.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-799f-29jm-gr6c", "reviewed": "2026-09-24" }, "F-NIMIQ-DHTGET-HANG-001": { "category": "resource-limits", "reason": "DHT query completion can remain stalled.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g39c-jcgg-qwvr", "reviewed": "2026-09-24" }, "F-NIMIQ-DISCOVERY-DOUBLE-SUBSTREAM-PANIC-001": { "category": "input-handling", "reason": "A repeated discovery substream violates an assumed state and panics.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-74hp-mhfx-m45h", "reviewed": "2026-09-24" }, "F-NIMIQ-DISCOVERY-EMPTY-ADDRLIST-PANIC-001": { "category": "input-handling", "reason": "An empty discovery address list reaches a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-c45m-6x25-3cjq", "reviewed": "2026-09-24" }, "F-NIMIQ-DISCOVERY-TIMESTAMP-POISON-001": { "category": "input-handling", "reason": "Discovery timestamps lack the required future-time range check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-hj3g-hh5f-63mp", "reviewed": "2026-09-24" }, "F-NIMIQ-HISTORYINDEX-PANIC-001": { "category": "input-handling", "reason": "History index input reaches a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-xr78-2jhh-9wf9", "reviewed": "2026-09-24" }, "F-NIMIQ-HISTORYPROOF-PANIC-001": { "category": "input-handling", "reason": "Malformed history proof input triggers a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-264v-m8fm-76jm", "reviewed": "2026-09-24" }, "F-NIMIQ-HISTORYSYNC-PANIC-001": { "category": "input-handling", "reason": "History synchronization input violates parser state assumptions.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-j99g-7rqw-q9jg", "reviewed": "2026-09-24" }, "F-NIMIQ-INTERLINK-001": { "category": "verification", "reason": "Macro block proposal verification omits the interlink commitment check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gr83-j5f8-p2r5", "reviewed": "2026-09-24" }, "F-NIMIQ-MACROCHAIN-001": { "category": "input-handling", "reason": "Macro-chain input reaches an invalid state and panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-48m6-486p-9j8p", "reviewed": "2026-09-24" }, "F-NIMIQ-PROPOSAL-001": { "category": "input-handling", "reason": "A signer-index boundary error triggers a checked-language panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-g99c-h7j7-rfhv", "reviewed": "2026-09-24" }, "F-NIMIQ-REQRES-INBOUNDLEAK-001": { "category": "resource-limits", "reason": "Inbound request channels retain resources after their useful lifetime.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-w5f8-87h2-m573", "reviewed": "2026-09-24" }, "F-NIMIQ-REQRES-STREAMS-STALL-001": { "category": "resource-limits", "reason": "Request/response streams can remain blocked without an effective limit.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-gh7r-qh4p-q4fr", "reviewed": "2026-09-24" }, "F-NIMIQ-ROGUEKEY-001": { "category": "verification", "reason": "New voting keys are accepted without proof of knowledge.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-pf4j-pf3w-95f9", "reviewed": "2026-09-24" }, "F-NIMIQ-SCANQR-JSREDIRECT-001": { "category": "access-control", "reason": "A scanned cashlink bypasses the intended navigation-domain check.", "source": "https://github.com/nimiq/wallet/commit/df954de", "reviewed": "2026-09-24" }, "F-NIMIQ-SKIPBLOCK-QUORUMBYPASS-001": { "category": "verification", "reason": "A truncated signer bitset bypasses a quorum check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-6973-8887-87ff", "reviewed": "2026-09-24" }, "F-NIMIQ-TENDERMINT-001": { "category": "verification", "reason": "Proposal validation omits a required root check.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7wh6-rmxx-ww47", "reviewed": "2026-09-24" }, "F-NIMIQ-VALIDATORSKEY-PANIC-001": { "category": "input-handling", "reason": "Malformed validator-key input triggers a panic.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-7c4j-2m43-2mgh", "reviewed": "2026-09-24" }, "F-NIMIQ-VESTING-MINCAP-UNDERFLOW-001": { "category": "input-handling", "reason": "Vesting arithmetic underflow triggers a panic; memory corruption is not asserted.", "source": "https://github.com/nimiq/core-rs-albatross/security/advisories/GHSA-vc34-39q2-m6q3", "reviewed": "2026-09-24" }, "F-NITRO-CMS-001": { "category": "resource-limits", "reason": "Ciphertext size controls an unbounded stack allocation.", "source": "https://github.com/aws/aws-nitro-enclaves-sdk-c/commit/b5ea92c368d565191c09ffff41275b6dc769ccb6", "reviewed": "2026-09-24" }, "F-NITRO-IVLEN-001": { "category": "memory-safety", "reason": "A short IV buffer reaches a cryptographic out-of-bounds read.", "source": "https://github.com/aws/aws-nitro-enclaves-sdk-c/pull/167", "reviewed": "2026-09-24" }, "F-NOTARYPROJECT-KYVERNO-001": { "category": "verification", "reason": "A premature loop return skips verification of later images.", "source": "https://github.com/kyverno/kyverno/pull/16208", "reviewed": "2026-09-24" }, "F-OPENCLAW-001": { "category": "path-traversal", "reason": "Mirroring resolves a path outside the intended directory.", "source": "https://github.com/openclaw/openclaw/security/advisories/GHSA-xw4p-pw82-hqr7", "reviewed": "2026-09-24" }, "F-OPENSSL-ASN1-001": { "category": "general-hardening", "reason": "Fuzz-corpus coverage is an authored testing contribution, not a newly established defect.", "source": "https://github.com/openssl/fuzz-corpora/pull/32", "reviewed": "2026-09-24" }, "F-OPENSSL-NC-SMTPUTF8MAILBOX-001": { "category": "verification", "reason": "Unsupported email name-constraint forms must be rejected.", "source": "https://github.com/openssl/openssl/pull/30329", "reviewed": "2026-09-24" }, "F-OPENSSL-NC-URI-AUTHORITY-001": { "category": "verification", "reason": "URI authority parsing misidentifies the hostname for name constraints.", "source": "https://github.com/openssl/openssl/pull/30319", "reviewed": "2026-09-24" }, "F-OPENSSL-OCSP-001": { "category": "verification", "reason": "Stapled OCSP verification accepts an unauthorized delegated responder.", "source": "/research/advisories/1SEAL-2026-009", "reviewed": "2026-09-24" }, "F-OPENSSL-SRTPKDF-002": { "category": "memory-safety", "reason": "SRTP KDF buffer use lacks required input-length validation.", "source": "https://github.com/openssl/openssl/pull/30001", "reviewed": "2026-09-24" }, "F-ORAS-AUTH-001": { "category": "ssrf", "reason": "Bearer realm URLs allow internal-network requests and TLS downgrade.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-xf85-363p-868w", "reviewed": "2026-09-24" }, "F-ORAS-LOCATION-UPLOAD-001": { "category": "ssrf", "reason": "An unvalidated upload Location receives forwarded credentials.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-jxpm-75mh-9fp7", "reviewed": "2026-09-24" }, "F-ORAS-SYMLINK-WRITE-001": { "category": "path-traversal", "reason": "A symlink permits file-store writes outside workingDir.", "source": "https://github.com/oras-project/oras-go/security/advisories/GHSA-8xwf-rjm4-xvhv", "reviewed": "2026-09-24" }, "F-OTELCOLLECTOR-001": { "category": "resource-limits", "reason": "Snappy decoded allocation occurs before the request-body size cap.", "source": "https://github.com/open-telemetry/opentelemetry-collector/pull/15253", "reviewed": "2026-09-24" }, "F-OTELCOLLECTORCONTRIB-001": { "category": "path-traversal", "reason": "Windows path handling escapes the intended file boundary.", "source": "https://github.com/open-telemetry/opentelemetry-collector-contrib/commit/d3308cffca3a9dccbafe1ca1b8d7a30420d0948b", "reviewed": "2026-09-24" }, "F-OTELGO-001": { "category": "resource-limits", "reason": "Baggage handling permits disproportionate resource consumption.", "source": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-mh2q-q3fh-2475", "reviewed": "2026-09-24" }, "F-OTELGO-002": { "category": "resource-limits", "reason": "Exporter response bodies are read without an effective bound.", "source": "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w8rr-5gcm-pp58", "reviewed": "2026-09-24" }, "F-PODMAN-001-007": { "category": "path-traversal", "reason": "Archive extraction can overwrite unrelated local files.", "source": "https://github.com/podman-container-tools/container-libs/security/advisories/GHSA-3gcv-x57j-xqxv", "reviewed": "2026-09-24" }, "F-PROMETHEUS-RELABEL-001": { "category": "resource-limits", "reason": "Repeated relabel processing permits excessive work.", "source": "https://github.com/prometheus/prometheus/pull/17969", "reviewed": "2026-09-24" }, "F-PROTOBUF-UPB-STRTOF-LOCALE-OVERFLOW-001": { "category": "memory-safety", "reason": "Locale-dependent numeric conversion overflows its destination buffer.", "source": "https://github.com/protocolbuffers/protobuf/commit/880f66e172347ac432dd5a2c07c38aa67dc95813", "reviewed": "2026-09-24" }, "F-PROTON-ANDROID-PASS-PASSKEY-ORIGIN-001": { "category": "access-control", "reason": "The signing request does not establish the caller's authorized WebAuthn origin.", "source": "https://github.com/protonpass/android-pass/commit/855c602584bd3ed8306a6ad5699fc770ada9baf3", "reviewed": "2026-09-24" }, "F-PROTON-DRIVE-SDK-001": { "category": "verification", "reason": "Public-share key-packet handling falls back after failed verification.", "source": "https://github.com/ProtonDriveApps/sdk/commit/451c1bf", "reviewed": "2026-09-24" }, "F-PROTON-WEBCL-001": { "category": "injection", "reason": "Unescaped class/style attribute values enter generated iframe HTML.", "source": "https://github.com/ProtonMail/WebClients/blob/008dfe64b21da7e0d64bc21572b5cbacb09deeab/packages/mail-renderer/helpers/getIframeHtml.ts", "reviewed": "2026-09-24" }, "F-PURPLELLAMA-003": { "category": "injection", "reason": "Untrusted values reach eval instead of literal-only parsing.", "source": "https://github.com/meta-llama/PurpleLlama/commit/48fa920b7acee37eb7acce2c797f7faded6213a0", "reviewed": "2026-09-24" }, "F-PYCA-CRYPTOGRAPHY-NAMECONSTRAINTS-WILDCARD-001": { "category": "verification", "reason": "Wildcard DNS names bypass certificate name constraints.", "source": "https://github.com/pyca/cryptography/security/advisories/GHSA-m959-cc7f-wv43", "reviewed": "2026-09-24" }, "F-QEMU-001-001": { "category": "memory-safety", "reason": "Mapped physical-memory length is not checked before the affected access.", "source": "https://github.com/qemu/qemu/commit/4f28b87fdd24df2049626106b7c24d0180952115", "reviewed": "2026-09-24" }, "F-REKOR-SSRF-001": { "category": "ssrf", "reason": "The public-key URL controls an outbound request destination.", "source": "https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j", "reviewed": "2026-09-24" }, "F-REKOR-VERIFY-002": { "category": "input-handling", "reason": "The recorded change adds a type assertion at the entry-bundle boundary.", "source": "https://github.com/sigstore/rekor/pull/2755", "reviewed": "2026-09-24" }, "F-RUSTLS-WEBPKI-001": { "category": "verification", "reason": "CRL authority matching is incomplete.", "source": "https://github.com/rustls/webpki/pull/469", "reviewed": "2026-09-24" }, "F-RUSTLS-WEBPKI-NAMECONSTRAINTS-URI-001": { "category": "verification", "reason": "URI name constraints are not enforced as required.", "source": "https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5", "reviewed": "2026-09-24" }, "F-RUSTLS-WEBPKI-NAMECONSTRAINTS-WILDCARD-001": { "category": "verification", "reason": "Wildcard DNS names bypass constraint checks.", "source": "https://github.com/rustls/webpki/security/advisories/GHSA-xgp8-3hg3-c2mh", "reviewed": "2026-09-24" }, "F-SEALED-SECRETS-ROTATE-SCOPE-001": { "category": "access-control", "reason": "Rotation can widen a namespace-scoped secret to cluster scope.", "source": "https://github.com/bitnami-labs/sealed-secrets/security/advisories/GHSA-465p-v42x-3fmj", "reviewed": "2026-09-24" }, "F-SIG-004-002": { "category": "verification", "reason": "A log-data decoding failure is not handled fail-closed during verification.", "source": "https://github.com/sigstore/sigstore-go/pull/562", "reviewed": "2026-09-24" }, "F-SIG-014-001": { "category": "verification", "reason": "RFC3161 verification accepts the recorded revoked timestamp signer.", "source": "https://github.com/sigstore/cosign/pull/4642", "reviewed": "2026-09-24" }, "F-SIG-016-001": { "category": "verification", "reason": "An unanchored identity regex accepts a partial certificate-identity match.", "source": "https://github.com/sigstore/sigstore-go/pull/558", "reviewed": "2026-09-24" }, "F-SIG-034-001": { "category": "verification", "reason": "An empty log URL disables a required verification step.", "source": "https://github.com/sigstore/policy-controller/pull/1923", "reviewed": "2026-09-24" }, "F-SIG-036-001": { "category": "verification", "reason": "A valid log entry is accepted without the required binding to the verified object.", "source": "https://github.com/sigstore/cosign/security/advisories/GHSA-whqx-f9j3-ch6m", "reviewed": "2026-09-24" }, "F-SIG-038-001": { "category": "input-handling", "reason": "An empty COSE message reaches a nil dereference.", "source": "https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833", "reviewed": "2026-09-24" }, "F-SIG-040-001": { "category": "verification", "reason": "Clock-drift evidence is not applied as an issuance gate.", "source": "https://github.com/sigstore/timestamp-authority/pull/1276", "reviewed": "2026-09-24" }, "F-SIG-GO-000-001": { "category": "resource-limits", "reason": "An unbounded transparency-log entry set consumes excessive resources.", "source": "https://github.com/sigstore/sigstore-go/pull/567", "reviewed": "2026-09-24" }, "F-SIG-GO-004": { "category": "input-handling", "reason": "Malformed PEM input reaches a nil dereference.", "source": "https://github.com/sigstore/sigstore-go/pull/566", "reviewed": "2026-09-24" }, "F-SIG-GO-THRESHOLD-001": { "category": "verification", "reason": "Timestamp verification does not enforce the minimum integrated-time threshold.", "source": "https://github.com/sigstore/sigstore-go/pull/590", "reviewed": "2026-09-24" }, "F-SIG-JS-TLOGTIME-001": { "category": "verification", "reason": "An unsigned integratedTime influences certificate-time validation.", "source": "https://github.com/sigstore/sigstore-js/security/advisories/GHSA-xgjw-pm74-86q4", "reviewed": "2026-09-24" }, "F-SIGANDROID-INTENT-001": { "category": "access-control", "reason": "An exported updater receiver accepts callers outside the intended boundary.", "source": "https://github.com/signalapp/Signal-Android/commit/fecb30a86eaa984e9495a486555150a9c4bc9b08", "reviewed": "2026-09-24" }, "F-SIGNAL-DESKTOP-EXPIRE-001": { "category": "input-handling", "reason": "Expiration-state handling fails to enforce the intended version cutoff.", "source": "https://github.com/signalapp/Signal-Desktop/commit/c863dfa66bdfdf636d9a218cdd263b0cc997fb1a", "reviewed": "2026-09-24" }, "F-SIGNAL-SERVER-PREKEY-001": { "category": "needs-detail", "reason": "Key-ID validation and key-depletion semantics are different mechanisms; the public mapping does not resolve which applies.", "source": "https://github.com/signalapp/Signal-Server/commit/b7d455ed114069ddff0e21b3ddfd7eaf6cc3994d", "reviewed": "2026-09-24" }, "F-SIGSTORE-005": { "category": "path-traversal", "reason": "A target name escapes the local cache directory.", "source": "https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf", "reviewed": "2026-09-24" }, "F-SKAFFOLD-WEBHOOK-001": { "category": "access-control", "reason": "Removal narrows the preview deployment webhook's exposed control surface.", "source": "https://github.com/GoogleContainerTools/skaffold/commit/3e7c0304a175f6ad52524232bc26777cfd01978c", "reviewed": "2026-09-24" }, "F-SMALLSTEP-AK-EKU-001": { "category": "input-handling", "reason": "An empty EKU input reaches a panic, not an established authorization bypass.", "source": "https://github.com/smallstep/certificates/pull/2569", "reviewed": "2026-09-24" }, "F-SMALLSTEP-WEBHOOK-001": { "category": "ssrf", "reason": "Request-influenced webhook rendering controls the outbound destination.", "source": "https://github.com/smallstep/certificates/pull/2570", "reviewed": "2026-09-24" }, "F-SOCI-OOB-001": { "category": "memory-safety", "reason": "Span/checkpoint count mismatch permits a C heap out-of-bounds read.", "source": "https://github.com/awslabs/soci-snapshotter/commit/0a1984bb2ffb169a0d11d543a6dde85dfd6ba506", "reviewed": "2026-09-24" }, "F-SPIRE-HTTPCHALLENGE-001": { "category": "ssrf", "reason": "HTTP challenge handling reaches an untrusted request destination.", "source": "https://github.com/spiffe/spire/releases/tag/v1.14.2", "reviewed": "2026-09-24" }, "F-TEKTON-001-001": { "category": "path-traversal", "reason": "Git resolver traversal reaches files beyond the tenant's intended root.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-j5q5-j9gm-2w5c", "reviewed": "2026-09-24" }, "F-TEKTON-PANIC-001": { "category": "input-handling", "reason": "An oversized resolver name triggers a panic.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-cv4x-93xx-wgfj", "reviewed": "2026-09-24" }, "F-TEKTON-REGEX-001": { "category": "verification", "reason": "A partial regular-expression match weakens the verification policy.", "source": "https://github.com/tektoncd/pipeline/security/advisories/GHSA-rmx9-2pp3-xhcr", "reviewed": "2026-09-24" }, "F-TELEGRAM-DESKTOP-FFMPEG-FRAMEAREA-001": { "category": "resource-limits", "reason": "Decoded frame area needs a limit before allocating frame storage.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "F-TELEGRAM-DESKTOP-FFMPEG-LINESIZE-MEMCPY-001": { "category": "memory-safety", "reason": "A negative or invalid frame stride reaches a raw memory copy.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "F-TELEGRAM-DESKTOP-FILENAME-TRAVERSAL-001": { "category": "path-traversal", "reason": "Untrusted filenames require sanitization before local path use.", "source": "https://github.com/telegramdesktop/tdesktop/commit/82f9aa1a2a0970e48caf8d7f4a60284347a13d99", "reviewed": "2026-09-24" }, "F-TELEGRAM-E2E-001": { "category": "secret-handling", "reason": "Message-key comparison is not constant-time.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/9d33962c013e68dcecd8c26bb23ca232bc52c2a2", "reviewed": "2026-09-24" }, "F-TELEGRAM-INTOVF-001": { "category": "memory-safety", "reason": "Frame size/stride arithmetic is used before bounded frame storage checks.", "source": "https://github.com/telegramdesktop/tdesktop/commit/eeafe9761409592bc1af3fb485118328f1019054", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-BOTPAY-001": { "category": "access-control", "reason": "Payment user scripts are injected into frames outside the intended main-frame boundary.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/a8a308d7a6843cb41e4e0e76908e552a4aeb1ee9", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-FFMPEG-LINESIZE-MEMCPY-001": { "category": "memory-safety", "reason": "Negative frame strides reach planar copy/convert paths.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-FFMPEG-PREVIEW-PIXFMT-001": { "category": "input-handling", "reason": "Unsupported pixel layouts reach a conversion path that assumes planar YUV data.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/615becca7ae7", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-SECRETAPI-LOCKOUT-001": { "category": "input-handling", "reason": "Truncated secret-message flags reach a force unwrap.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/2dd07ef8cc79", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-SSRF-001": { "category": "ssrf", "reason": "Bot media URLs bypass the intended public-network destination boundary.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/6eb201465096", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-TGCALLS-SIGNALING-001": { "category": "resource-limits", "reason": "The recorded signaling change bounds timer backoff and gates writes; it is not independent proof of the report-to-fix mapping.", "source": "https://github.com/TelegramMessenger/tgcalls/commit/24fd51b", "reviewed": "2026-09-24" }, "F-TELEGRAM-IOS-TGLINK-001": { "category": "access-control", "reason": "The recorded removal eliminates a URL-controlled host override; exact fix mapping remains conditional.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/cbf8f6b", "reviewed": "2026-09-24" }, "F-TELEGRAM-JSBRIDGE-001": { "category": "injection", "reason": "Bridge result data is interpolated into JavaScript instead of serialized.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/687cefb2914539e2a42d3a10e91fe4ce1c7fbf7f", "reviewed": "2026-09-24" }, "F-TELEGRAM-OOM-001": { "category": "resource-limits", "reason": "Token-length underflow leads to an oversized allocation.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/09d3f7386b3c42651e792aa90d959c89cee4817e", "reviewed": "2026-09-24" }, "F-TELEGRAM-TL-001": { "category": "memory-safety", "reason": "TL parsing can read beyond an input buffer.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/8e9cd79855683efb9a3cbf14a1ecd637cfbf7b54", "reviewed": "2026-09-24" }, "F-TELEGRAM-VECOVF-001": { "category": "needs-detail", "reason": "The cited logging change does not implement the claimed vector-length check.", "source": "https://github.com/tdlib/td/commit/9722906f9a0bfc673eccd576050f299579e95602", "reviewed": "2026-09-24" }, "F-TELEGRAM-WEBAPP-001": { "category": "access-control", "reason": "A subframe can reach a bridge intended for the main frame.", "source": "https://github.com/TelegramMessenger/Telegram-iOS/commit/c5a0ad267cbd2a61a0d4548490f6af5521fa55df", "reviewed": "2026-09-24" }, "F-TELEGRAM-WEBK-TGIV-DECODE-001": { "category": "input-handling", "reason": "Unsafe or malformed links reach the local tg://iv decoding handler.", "source": "https://github.com/morethanwords/tweb/commit/6af7087389c08e9860ce17559915a7747ac99ac0", "reviewed": "2026-09-24" }, "F-TGAND-GIFVIDEO-001": { "category": "memory-safety", "reason": "Stride and conversion-context handling can access outside native video buffers; the related ID remains separately recorded.", "source": "https://github.com/DrKLO/Telegram/commit/63f86ef", "reviewed": "2026-09-24" }, "F-TGAND-GIFVIDEO-OOB-001": { "category": "memory-safety", "reason": "Stride and conversion-context handling can access outside native video buffers.", "source": "https://github.com/DrKLO/Telegram/commit/63f86ef", "reviewed": "2026-09-24" }, "F-TGAND-SECRETCHAT-VECTOR-001": { "category": "input-handling", "reason": "Vector-size validation is added at the secret-chat decoding boundary.", "source": "https://github.com/DrKLO/Telegram/commit/fb98f157afb3e5048bce4a9496104e5aed557686", "reviewed": "2026-09-24" }, "F-TGDESKTOP-CLIPBOARD-001": { "category": "access-control", "reason": "Clipboard reads need a recent genuine user interaction; the fix predates this report.", "source": "https://github.com/telegramdesktop/tdesktop/commit/d349a28d7645", "reviewed": "2026-09-24" }, "F-TGDESKTOP-REFLECTOR-001": { "category": "memory-safety", "reason": "Peer-tag length arithmetic underflows before memory access.", "source": "https://github.com/TelegramMessenger/tgcalls/commit/014653852e437a517bbb1c50063dc2518adf77f1", "reviewed": "2026-09-24" }, "F-TGDESKTOP-WEBVIEW-004": { "category": "access-control", "reason": "The mapped hardening limits app/shell/WebApp interaction origins; exact report coverage remains qualified.", "source": "https://github.com/telegramdesktop/tdesktop/commit/55768ee", "reviewed": "2026-09-24" }, "F-TGX-PATHTRAVERSAL-001": { "category": "path-traversal", "reason": "Filename handling returns the original rather than sanitized name.", "source": "https://github.com/TGX-Android/Telegram-X/commit/c3b01454df69", "reviewed": "2026-09-24" }, "F-TON-006-001": { "category": "resource-limits", "reason": "RLDP/FEC work is allocated before the required expiry/resource checks.", "source": "https://github.com/ton-blockchain/ton/pull/2191", "reviewed": "2026-09-24" }, "F-TON-009-001": { "category": "needs-detail", "reason": "A multi-fix change is mapped by date/area, without enough public detail for this exact report.", "source": "https://github.com/ton-blockchain/ton/pull/2208", "reviewed": "2026-09-24" }, "F-TON-010-001": { "category": "needs-detail", "reason": "Two public fix candidates remain; the exact mechanism is not established by the recorded mapping.", "source": "https://github.com/ton-blockchain/ton/pull/2211", "reviewed": "2026-09-24" }, "F-TORVALDS-LINUX-BT-HCI-001": { "category": "memory-safety", "reason": "HCI event handling lacks required buffer bounds validation.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-31771", "reviewed": "2026-09-24" }, "F-TORVALDS-LINUX-BT-SMP-001": { "category": "verification", "reason": "Pairing security state asserts MITM protection without establishing it.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-43334", "reviewed": "2026-09-24" }, "F-TORVALDS-LINUX-RXRPC-001": { "category": "memory-safety", "reason": "RxGK token loading omits required buffer bounds checks.", "source": "https://github.com/advisories/GHSA-p4pm-x7ch-5mvc", "reviewed": "2026-09-24" }, "F-TORVALDS-LINUX-TIPC-001": { "category": "input-handling", "reason": "Duplicate acknowledgements underflow bc_ackers and block later broadcasts; no memory corruption is asserted.", "source": "https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=48a5fe38772b6f039522469ee6131a67838221a8", "reviewed": "2026-09-24" }, "F-TRAEFIK-002": { "category": "ssrf", "reason": "An absolute health-check URL bypasses the intended destination boundary.", "source": "https://github.com/traefik/traefik/pull/12642", "reviewed": "2026-09-24" }, "F-TRAEFIK-003": { "category": "input-handling", "reason": "Case handling leaves hop-by-hop headers inconsistently processed.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-92mv-8f8w-wq52", "reviewed": "2026-09-24" }, "F-TRAEFIK-004": { "category": "resource-limits", "reason": "Incomplete TCP handshakes retain resources without an effective bound.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-xw98-5q62-jx94", "reviewed": "2026-09-24" }, "F-TRAEFIK-006": { "category": "injection", "reason": "Backticks in rule data change rule-expression interpretation.", "source": "https://github.com/traefik/traefik/security/advisories/GHSA-8q2w-wr49-whqj", "reviewed": "2026-09-24" }, "F-TREZOR-004": { "category": "display-binding", "reason": "Stellar signing confirmation does not bind the displayed operation details.", "source": "https://github.com/trezor/trezor-firmware/commit/663569c40b60d5dc62c14ae1b590ea9d54508aab", "reviewed": "2026-09-24" }, "F-TREZOR-005": { "category": "display-binding", "reason": "Confirmation covers the initial calldata chunk rather than the complete signed stream.", "source": "https://www.cve.org/CVERecord?id=CVE-2026-65058", "reviewed": "2026-09-24" }, "F-TREZOR-008": { "category": "memory-safety", "reason": "JPEG verification accesses memory outside the intended image buffer.", "source": "https://github.com/trezor/trezor-firmware/commit/fb4aa180cf6fb928138bc2cc2fc8386a7d337bc0", "reviewed": "2026-09-24" }, "F-TREZOR-009": { "category": "memory-safety", "reason": "DMA2D syscalls use insufficiently bounded buffers.", "source": "https://github.com/trezor/trezor-firmware/commit/e5c51d5ee4b33af859363afcfc104857956e8931", "reviewed": "2026-09-24" }, "F-TREZOR-011": { "category": "memory-safety", "reason": "The filter syscall lacks the required buffer bounds.", "source": "https://github.com/trezor/trezor-firmware/commit/f60f535403e6a2189a103017183224ad535b842f", "reviewed": "2026-09-24" }, "F-TREZOR-012": { "category": "memory-safety", "reason": "An image syscall uses insufficiently bounded memory.", "source": "https://github.com/trezor/trezor-firmware/commit/59d8d78ef785a60d5a01dcca974c2858ba432de2", "reviewed": "2026-09-24" }, "F-TREZOR-BIP32-001": { "category": "secret-handling", "reason": "Derived secret key material remains in a cache beyond its intended lifetime.", "source": "https://github.com/trezor/trezor-firmware/commit/26914ff4962812695a2abf49f06e268606a7a7e2", "reviewed": "2026-09-24" }, "F-TREZOR-BLOCKBOOK-001": { "category": "input-handling", "reason": "Negative range values reach invalid arithmetic/state.", "source": "https://github.com/trezor/blockbook/commit/496f8e0f3272ae604349fada565f0dff0cb78526", "reviewed": "2026-09-24" }, "F-TREZOR-BLOCKBOOK-API-SENDTX-READALL-001": { "category": "resource-limits", "reason": "Transaction submission bodies reach unbounded reads.", "source": "https://github.com/trezor/blockbook/commit/33b99cc7d4406be889551aa4645ea4ead7f3a004", "reviewed": "2026-09-24" }, "F-TREZOR-BLOCKBOOK-NFT-URI-XSS-001": { "category": "injection", "reason": "An NFT URI reaches executable markup without the required escaping.", "source": "https://github.com/trezor/blockbook/commit/e4fdb5ee25a58df3af52f250300cc6a6fced6d16", "reviewed": "2026-09-24" }, "F-TREZOR-BLOCKBOOK-WS-READLIMIT-001": { "category": "resource-limits", "reason": "WebSocket reads are not bounded by message size.", "source": "https://github.com/trezor/blockbook/commit/f8349fcebcdf2a9066a06245c1e68c67f3e608bd", "reviewed": "2026-09-24" }, "F-TREZOR-CRYPTO-MEMZERO-001": { "category": "secret-handling", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/bddd38b47d920559e50aa50c82eab62a8f6510ca", "reviewed": "2026-09-24" }, "F-TREZOR-CRYPTO-MEMZERO-002": { "category": "secret-handling", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/48db49fa67eb4b51a30dff394e27cbea6803dbf1", "reviewed": "2026-09-24" }, "F-TREZOR-CRYPTO-MEMZERO-003": { "category": "secret-handling", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/477cbb365a29c23df766fd8f128cc5b73ed04bb6", "reviewed": "2026-09-24" }, "F-TREZOR-CRYPTO-MEMZERO-005": { "category": "secret-handling", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/40d4f9027d3b5f05204afb3e11d9a4dc383fa50d", "reviewed": "2026-09-24" }, "F-TREZOR-CRYPTO-MEMZERO-006": { "category": "secret-handling", "reason": "Sensitive cryptographic buffers are not cleared on the affected path.", "source": "https://github.com/trezor/trezor-firmware/commit/09e55d8c9cb255eaa0463a8aa58f5dca1ed17644", "reviewed": "2026-09-24" }, "F-TREZOR-FW-007-001": { "category": "verification", "reason": "Multisignature verification fails to enforce the intended signer requirements.", "source": "https://github.com/trezor/trezor-firmware/commit/ab9b4feaff30747a37fd9222d627e8636c78641e", "reviewed": "2026-09-24" }, "F-TREZOR-SUITE-OAUTH-001": { "category": "access-control", "reason": "OAuth responses need state binding to their initiating request.", "source": "https://github.com/trezor/trezor-suite/commit/f02a8d4ceca54ac2c405a1cad8f3e00b3e748015", "reviewed": "2026-09-24" }, "F-TREZOR-SUITE-PM-001": { "category": "access-control", "reason": "Extension connectivity permits callers outside the intended trust boundary.", "source": "https://github.com/trezor/trezor-suite/commit/c84e94b607f35eb9b5c239d9af810b744308d575", "reviewed": "2026-09-24" }, "F-TREZOR-SUITE-PT-001": { "category": "path-traversal", "reason": "Untrusted path components escape the intended local directory.", "source": "https://github.com/trezor/trezor-suite/commit/cb76104f1068b7047591735ca691a7fed4439613", "reviewed": "2026-09-24" }, "F-TREZOR-SYSCALL-TRANSLATIONS-001": { "category": "memory-safety", "reason": "Translation syscall input reaches insufficiently bounded memory.", "source": "https://github.com/trezor/trezor-firmware/commit/1811d3bb96291dfe5cbecd442719d37bce6b74c3", "reviewed": "2026-09-24" }, "F-TREZOR-THP-DOS-001": { "category": "resource-limits", "reason": "Oversized protocol messages exhaust processing resources.", "source": "https://github.com/trezor/trezor-firmware/commit/15975901acf6d909baf3062d480fe865d023b438", "reviewed": "2026-09-24" }, "F-TREZOR-THP-FRAGMENT-001": { "category": "input-handling", "reason": "Fragment handling does not preserve the required payload length/checksum boundary.", "source": "https://github.com/trezor/trezor-firmware/commit/d63fe0e883771a1cebb7c15ec45e2445c1821682", "reviewed": "2026-09-24" }, "F-TRIVY-ACTION-001": { "category": "injection", "reason": "Untrusted environment content is sourced as shell code.", "source": "https://github.com/aquasecurity/trivy-action/security/advisories/GHSA-9p44-j4g5-cfx5", "reviewed": "2026-09-24" }, "F-TRIVY-CONFIG-TEMPLATE-001": { "category": "needs-detail", "reason": "The public title names a template-extension check, but does not establish the report's exact execution or path mechanism.", "source": "https://github.com/aquasecurity/trivy/commit/20458b836b71b2bed72d31ebba1ba9572333dcfd", "reviewed": "2026-09-24" }, "F-TRIVY-TF-FILE-001": { "category": "path-traversal", "reason": "Terraform file functions read outside the scan root.", "source": "https://github.com/aquasecurity/trivy/commit/9d91b888cf63023e9c09b64259a4c1cea8dfe993", "reviewed": "2026-09-24" }, "F-TRTLLM-DESER-001": { "category": "needs-detail", "reason": "The bulletin-to-report mapping is conditional and cannot establish this exact finding's mechanism.", "source": "https://nvidia.custhelp.com/app/answers/detail/a_id/5805/~/security-bulletin%3A-nvidia-tensorrt-llm---may-2026", "reviewed": "2026-09-24" }, "F-TSA-001-002": { "category": "verification", "reason": "Timestamp certificate validation does not reject the recorded revocation case.", "source": "https://github.com/sigstore/timestamp-authority/pull/1277", "reviewed": "2026-09-24" }, "F-TUF-001": { "category": "verification", "reason": "Delegated signature threshold enforcement is incomplete.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-fphv-w9fq-2525", "reviewed": "2026-09-24" }, "F-TUF-002": { "category": "access-control", "reason": "Cache-file permissions permit unintended local access.", "source": "https://github.com/theupdateframework/go-tuf/commit/f400bf4c20476804475d34239f01212e1041ec38", "reviewed": "2026-09-24" }, "F-TUF-003": { "category": "input-handling", "reason": "Malformed repository input reaches an assertion failure.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-846p-jg2w-w324", "reviewed": "2026-09-24" }, "F-TUF-008": { "category": "path-traversal", "reason": "A repository name crosses the intended cache-path boundary.", "source": "https://github.com/theupdateframework/go-tuf/security/advisories/GHSA-jqc5-w2xx-5vq4", "reviewed": "2026-09-24" }, "F-TUF-009": { "category": "verification", "reason": "Empty target hashes are accepted without the required integrity commitment.", "source": "https://github.com/theupdateframework/go-tuf/pull/721", "reviewed": "2026-09-24" }, "F-TUF-PYTUF-002": { "category": "verification", "reason": "Bootstrap handling requires an explicit trusted starting point.", "source": "https://github.com/theupdateframework/python-tuf/pull/2903", "reviewed": "2026-09-24" }, "F-UEFI-FIRMWARE-TIANO-MAKETABLE-OOBW-002": { "category": "memory-safety", "reason": "Tiano MakeTable writes outside the intended buffer.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "F-UEFI-FIRMWARE-TIANO-READCLEN-OOBW-003": { "category": "memory-safety", "reason": "Tiano ReadCLen writes outside the intended buffer.", "source": "/research/advisories/1SEAL-2026-010", "reviewed": "2026-09-24" }, "F-VAULT-ACME-EAB-PANIC-001": { "category": "input-handling", "reason": "Malformed external-account-binding input triggers a panic.", "source": "https://github.com/hashicorp/vault/commit/daa03407c0d8042105f8af4df0a6c5e056482db0", "reviewed": "2026-09-24" }, "F-VAULT-ACME-SSRF-001": { "category": "ssrf", "reason": "ACME validation dials attacker-controlled DNS destinations.", "source": "https://github.com/advisories/GHSA-8r5m-3f66-qpr3", "reviewed": "2026-09-24" }, "F-VAULT-AUTHZ-BEARER-TOKEN-LEAK-001": { "category": "secret-handling", "reason": "An authorization bearer token is exposed through backend header forwarding.", "source": "https://discuss.hashicorp.com/t/hcsec-2026-07-vault-may-expose-tokens-to-auth-plugins-due-to-incorrect-header-sanitization/77344", "reviewed": "2026-09-24" }, "F-VSCODE-COPILOT-001": { "category": "needs-detail", "reason": "Public CVE credit is recorded, but its multiple advisory variants do not establish this finding's exact mechanism.", "source": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21523", "reviewed": "2026-09-24" }, "F-VSCODE-MCP-001": { "category": "access-control", "reason": "The recorded report concerns bypassing the MCP workspace trust boundary.", "source": "https://github.com/microsoft/vscode/security/advisories/GHSA-6xq8-9qf3-p6qv", "reviewed": "2026-09-24" }, "F-WEBA-POSTMSG-001": { "category": "access-control", "reason": "Incoming iframe messages require source/origin binding; outbound targetOrigin coverage remains unconfirmed.", "source": "https://github.com/Ajaxy/telegram-tt/commit/7e789e6", "reviewed": "2026-09-24" }, "F-WOLFSSL-ALPN-001": { "category": "memory-safety", "reason": "The published advisory describes an out-of-bounds read in ALPN list parsing.", "source": "https://github.com/advisories/GHSA-f377-557w-vjgv", "reviewed": "2026-09-24" }, "F-WOLFSSL-CRL-001": { "category": "verification", "reason": "Unknown critical CRL extensions are not rejected as required.", "source": "https://github.com/wolfSSL/wolfssl/pull/10239", "reviewed": "2026-09-24" }, "F-WOLFSSL-ECH-001": { "category": "memory-safety", "reason": "An ECH length underflow produces a heap out-of-bounds write.", "source": "https://github.com/advisories/GHSA-j2g5-52p7-mfpc", "reviewed": "2026-09-24" }, "F-WOLFSSL-NC-URI-001": { "category": "verification", "reason": "URI name-constraint parsing fails to enforce the intended certificate boundary.", "source": "https://github.com/advisories/GHSA-9xmr-c663-3rpr", "reviewed": "2026-09-24" }, "F-WOLFSSL-NC-WILDCARD-001": { "category": "verification", "reason": "Wildcard certificate names bypass name-constraint checks.", "source": "https://github.com/wolfSSL/wolfssl/pull/9991", "reviewed": "2026-09-24" }, "F-ZEPHYR-BLE-001": { "category": "memory-safety", "reason": "The recorded BLE issue involves an out-of-bounds memory access.", "source": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/GHSA-qrcq-hxwj-mqxm", "reviewed": "2026-09-24" }, "F-ZOT-AUTHZ-001": { "category": "access-control", "reason": "Create permission can be used to overwrite existing content.", "source": "https://github.com/project-zot/zot/security/advisories/GHSA-85jx-fm8m-x8c6", "reviewed": "2026-09-24" }, "F-ARGOCD-REPOCREDS-001": { "category": "needs-detail", "reason": "Technical mechanism withheld during coordination; this record documents only the CVE request status.", "source": "/research/policy/", "reviewed": "2026-10-06" }, "F-OVERLAYBD-001-002": { "category": "memory-safety", "reason": "Untrusted LSMT index metadata can overflow index_bytes and cause out-of-bounds heap access.", "source": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/107xxx/CVE-2026-107446.json", "reviewed": "2026-10-08" }, "F-WOLFSSL-CRL-SCOPE-COLLAPSE-001": { "category": "verification", "reason": "Unknown critical CRL extensions are not rejected as required.", "source": "https://github.com/wolfSSL/wolfssl/pull/10239", "reviewed": "2026-09-24" }, "F-TORVALDS-LINUX-NFC-001": { "category": "memory-safety", "reason": "The LLCP TLV parsers read headers and payloads without required buffer bounds checks.", "source": "https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net/+/78b20c8eeacd2e44a2d8a4cb5316d3c521d90911", "reviewed": "2026-10-07" }, "F-FLUTTER-APNG-002": { "category": "memory-safety", "reason": "Unchecked multiplication can produce an incorrect APNG frame buffer size.", "source": "https://github.com/flutter/flutter/commit/79ab0aabbc8452461f115d18731138d403cad987", "reviewed": "2026-10-07" }, "F-UEFI-FIRMWARE-PATH-TRAVERSAL-001": { "category": "path-traversal", "reason": "Firmware-controlled path components can escape the intended extraction directory.", "source": "https://github.com/theopolis/uefi-firmware-parser/commit/86d283452c8deceb4e854fd16433748c74638a5c", "reviewed": "2026-10-07" }, "F-UEFI-FIRMWARE-PATH-TRAVERSAL-002": { "category": "path-traversal", "reason": "Firmware-controlled path components can escape the intended extraction directory.", "source": "https://github.com/theopolis/uefi-firmware-parser/commit/86d283452c8deceb4e854fd16433748c74638a5c", "reviewed": "2026-10-07" }, "F-PROMETHEUS-SCALEWAY-SD-001": { "category": "ssrf", "reason": "The HTTP client must preserve the explicitly configured redirect behavior.", "source": "https://github.com/prometheus/prometheus/pull/18539", "reviewed": "2026-10-07" }, "F-BAZEL-001-004": { "category": "access-control", "reason": "An explicitly enabled debugger should not accept network connections beyond its intended local scope by default.", "source": "https://github.com/bazelbuild/bazel/commit/a6836fe459ae01cf5426982e08615e05c94e8c67", "reviewed": "2026-10-07" }, "F-AWS-NPA-001": { "category": "input-handling", "reason": "Ambiguous pod/namespace keys can associate distinct objects with the same policy-tracking state.", "source": "https://github.com/aws/aws-network-policy-agent/pull/563", "reviewed": "2026-10-07" }, "F-NPA-FAILOPEN-001": { "category": "input-handling", "reason": "A failed policy-map update must return an error so its caller does not treat incomplete enforcement as success.", "source": "https://github.com/aws/aws-network-policy-agent/pull/562", "reviewed": "2026-10-07" }, "F-DCRLND-CHAINVIEW-DEADLOCK-001": { "category": "resource-limits", "reason": "An error return with the filter mutex still held can stall later chain-view operations.", "source": "https://github.com/decred/dcrlnd/commit/d11b48570880053b9348481c90370aba4b76bec9", "reviewed": "2026-10-07" }, "F-GRPC-001": { "category": "resource-limits", "reason": "Decompression can allocate beyond the configured maximum message length before rejecting the RPC.", "source": "https://github.com/grpc/grpc/security/advisories/GHSA-hf3w-6hpw-qp67", "reviewed": "2026-10-07" }, "F-FIREFOX-IPC-MLS-009": { "category": "verification", "reason": "MLS IPC checks whether the submitted principal could be loaded by the sending process remote type; this is the public hardening scope, not proof of independent cross-process exploitation.", "source": "https://bugzilla.mozilla.org/show_bug.cgi?id=2020535", "reviewed": "2026-10-07" }, "F-TRUSTWALLET-CBOR-001": { "category": "input-handling", "reason": "CBOR length handling.", "source": "https://github.com/trustwallet/wallet-core/pull/4707", "reviewed": "2026-10-07" }, "F-TRUSTWALLET-PUBKEY-001": { "category": "verification", "reason": "ECDSA message-length validation.", "source": "https://github.com/trustwallet/wallet-core/pull/4693", "reviewed": "2026-10-07" } }, "pending_disclosures": [ { "finding_id": "F-ARGOCD-REPOCREDS-001", "repo": "argoproj/argo-cd", "title": "Private report; CVE assignment requested", "status": "disclosure pending", "submitted": "2026-03-05", "note": "Researcher-confirmed CVE request for a private report filed on 5 March 2026. The public finding ID may identify a component. This limited process-status record is published under the case-specific exception in 1seal's disclosure policy. No assigned CVE, public vendor disposition, affected versions, or fix is asserted. The vulnerability mechanism, reproduction steps, and exploit details remain withheld.", "classification": { "area": "unclassified", "reason": "The finding ID alone does not establish a security area; no public technical evidence is supplied for assigning one.", "source": "/research/policy/", "reviewed": "2026-10-06" }, "cve_request": { "schema_version": "1.0", "state": "requested", "authority": "MITRE", "confirmation": "researcher-confirmed submission", "recorded_at": "2026-10-06" }, "record_type": "pending", "counted": false, "canonical_url": "https://1seal.org/research/findings/F-ARGOCD-REPOCREDS-001/", "source_url": null, "disclosed": null, "cwe": null, "layer": "unclassified" } ], "schema_version": "5.0", "classification_rules": { "unit": "one primary mechanism per finding ID; multiple records for the same ID count once", "boundary": "editorial topics of recorded public evidence, not vendor severity, independent vulnerability counts, credit or fix confirmation", "other": "general-hardening and needs-detail are separate dispositions, not defect mechanisms", "legacy": "record classification.area and layer describe the security area, not the failure mechanism; old layer links remain supported", "categories": { "verification": { "label": "Verification failures", "description": "Signature, certificate, proof or policy-evidence validation.", "mechanism": true }, "access-control": { "label": "Access control", "description": "Principal, origin, permission or tenant-boundary enforcement.", "mechanism": true }, "path-traversal": { "label": "File / path escapes", "description": "Filesystem paths escaping their intended root.", "mechanism": true }, "memory-safety": { "label": "Memory safety", "description": "Out-of-bounds access, unsafe lifetime or buffer arithmetic.", "mechanism": true }, "injection": { "label": "Code / markup injection", "description": "Untrusted data interpreted as code, commands or markup.", "mechanism": true }, "ssrf": { "label": "Outbound request trust", "description": "Untrusted destinations, redirects or credentials sent to those destinations.", "mechanism": true }, "resource-limits": { "label": "Resource limits", "description": "Unbounded allocation, work, retained resources or stalled operations.", "mechanism": true }, "input-handling": { "label": "Input / state handling", "description": "Malformed input, range or state handling without a more specific mechanism established.", "mechanism": true }, "secret-handling": { "label": "Secret handling", "description": "Secret retention, exposure, timing or transport protection.", "mechanism": true }, "display-binding": { "label": "Display / action mismatch", "description": "User-visible confirmation not bound to the committed payload.", "mechanism": true }, "general-hardening": { "label": "General hardening / testing", "description": "Engineering work without a specific defect mechanism established here.", "mechanism": false }, "needs-detail": { "label": "Needs source detail", "description": "The recorded public evidence does not support a specific classification yet.", "mechanism": false } } }, "classification_counts": { "verification": 67, "access-control": 39, "path-traversal": 33, "memory-safety": 41, "injection": 10, "ssrf": 16, "resource-limits": 32, "input-handling": 44, "secret-handling": 14, "display-binding": 6, "general-hardening": 12, "needs-detail": 10 }, "snapshot_date": "2026-10-08", "counting_rules": { "url": "/research/#counting", "headline": "counted CVE and GHSA advisory records + security PRs + credited fixes + report-associated fixes + hardening/testing records", "roles": "PR and engineering buckets include researcher-opened and vendor-opened work, not an authorship total. PR opener, code authorship and reporting credit are distinct. v4 renames counts.authored_contribs to counts.engineering_contribs without changing membership.", "fix_boundary": "Report-associated fixes include conditional mappings and partial mitigations. Their total is not a count of independently reproduced fixes, released fixes or verified deployments; read each record status and limits.", "dates": "snapshot_date is the portfolio data revision, not a claim that all upstream facts were rechecked that day. Per-source observations and editorial review dates are separate; deployment revision is in /_build.json.", "exclusions": "long-form 1seal advisory pages and historical fixes do not add headline records; advisory exclude_from_counts is respected", "visible_records": "Research excludes advisories_detailed as article rows. Each write-up with finding IDs absent from other records contributes one uncounted Documented finding row for its remaining IDs; repeated IDs are not added again. Write-ups remain in this payload and on finding evidence pages. v5 changes visible_records and area/project distributions, not headline membership.", "finding_ids": "mechanically deduplicated identifiers, not a deduplicated count of independent vulnerabilities", "projects": "distinct repositories in headline sections, including excluded advisory records", "cves": "CVE publication state must be PUBLISHED in the source-bound registry snapshot; RESERVED, REJECTED and unverified IDs do not count as CVEs. A published GHSA can still count once in the GHSA bucket." }, "counts": { "records": 335, "projects": 156, "cves": 112, "ghsas": 12, "prs": 29, "credited_fixes": 15, "engineering_contribs": 5, "upstream_contribs": 20, "reported_fixes": 162, "visible_records": 341, "unique_findings": 324 } }