Approved changes feed: RSS · Atom

cpe:2.3:a:telnyx:telnyx:4.87.1:*:*:*:*:python:*:*

part: a version: 4.87.1 update: *

VendorTelnyx (5bdd4f45-9f3a-5873-a4e5-c8bde628772d)
ProductTelnyx (2d574bea-1982-5cfb-b43a-52000def5085)
Edition*
Language*
Software edition*
Target softwarepython
Target hardware*
Other*

Notes

Imported from NVD CPE 2.0 feed

PURL mappings

PURLSourceLast updated
pkg:gem/telnyx purl2cpe 2026-06-01 10:12:51.327931
pkg:github/team-telnyx/telnyx-go purl2cpe 2026-06-01 10:12:51.327934
pkg:github/team-telnyx/telnyx-java purl2cpe 2026-06-01 10:12:51.327938
pkg:github/team-telnyx/telnyx-node purl2cpe 2026-06-01 10:12:51.327941
pkg:github/team-telnyx/telnyx-php purl2cpe 2026-06-01 10:12:51.327945
pkg:github/team-telnyx/telnyx-python purl2cpe 2026-06-01 10:12:51.327948
pkg:github/team-telnyx/telnyx-ruby purl2cpe 2026-06-01 10:12:51.327952
pkg:golang/github.com/team-telnyx/telnyx-go purl2cpe 2026-07-28 16:40:56.448219
pkg:maven/com.telnyx.sdk/telnyx purl2cpe 2026-06-01 10:12:51.327955
pkg:npm/telnyx purl2cpe 2026-06-01 10:12:51.327959
pkg:pypi/telnyx purl2cpe 2026-06-01 10:12:51.327962

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-33634 vulnerable 2026-06-08 07:59:10.517818 Trivy ecosystem supply chain briefly compromised
Trivy is a security scanner. On March 19, 2026, a threat actor used compromised credentials to publish a malicious Trivy v0.69.4 release, force-push 76 of 77 version tags in `aquasecurity/trivy-action` to credential-stealing malware, and replace all 7 tags in `aquasecurity/setup-trivy` with malicious commits. This incident is a continuation of the supply chain attack that began in late February 2026. Following the initial disclosure on March 1, credential rotation was performed but was not atomic (not all credentials were revoked simultaneously). The attacker could have use a valid token to exfiltrate newly rotated secrets during the rotation window (which lasted a few days). This could have allowed the attacker to retain access and execute the March 19 attack. Affected components include the `aquasecurity/trivy` Go / Container image version 0.69.4, the `aquasecurity/trivy-action` GitHub Action versions 0.0.1 – 0.34.2 (76/77), and the`aquasecurity/setup-trivy` GitHub Action versions 0.2.0 – 0.2.6, prior to the recreation of 0.2.6 with a safe commit. Known safe versions include versions 0.69.2 and 0.69.3 of the Trivy binary, version 0.35.0 of trivy-action, and version 0.2.6 of setup-trivy. Additionally, take other mitigations to ensure the safety of secrets. If there is any possibility that a compromised version ran in one's environment, all secrets accessible to affected pipelines must be treated as exposed and rotated immediately. Check whether one's organization pulled or executed Trivy v0.69.4 from any source. Remove any affected artifacts immediately. Review all workflows using `aquasecurity/trivy-action` or `aquasecurity/setup-trivy`. Those who referenced a version tag rather than a full commit SHA should check workflow run logs from March 19–20, 2026 for signs of compromise. Look for repositories named `tpcp-docs` in one's GitHub organization. The presence of such a repository may indicate that the fallback exfiltration mechanism was triggered and secrets were successfully stolen. Pin GitHub Actions to full, immutable commit SHA hashes, don't use mutable version tags.
Published: 2026-03-23T21:47:29.636Z
Updated: 2026-03-30T14:40:28.027Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.