major vulnerability· requires attention

Abuse of GitHub Actions 'pull_request_target' can exfiltrate repo secrets and tokens across organizations; impacts many code repositories and integrations, likely to cause wide disruption.

Cloud

CVE-2026-83493

9.1

Critical

EPSS n/a

pull_request_target workflows can be abused to exfiltrate repository secrets and tokens

exploited

No known exploitation not in CISA KEV as of our last sync

fix

No fixed release stated by the publisher

likelihood

No EPSS score yet

Published 6 Nov 2026Analysed here 7 Nov 2026CVSS scored by CISA

common questions

Is CVE-2026-83493 being exploited?

Not confirmed. CVE-2026-83493 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-83493?

CVE-2026-83493 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-83493?

Not known from our data. No patch reference has been recorded for CVE-2026-83493, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-83493 affect?

CVE-2026-83493 affects distributed-workloads, GitHub Actions 'pull_request_target' workflows, Repositories using SNYK_TOKEN or default write tokens. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-83493?

Remove secrets from workflows, avoid pull_request_target for untrusted PRs, rotate tokens, apply vendor fixes when published

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary

technical analysis

affected

distributed-workloadsGitHub Actions 'pull_request_target' workflowsRepositories using SNYK_TOKEN or default write tokens

impact

Remote attacker submits crafted PR to exfiltrate secrets (SNYK_TOKEN, default write token), hijack Snyk integration, and gain repo control.

action required

Immediate action required

cisa ssvc

exploitation: none
automatable: yes
technical impact: total

Assessed by CISA 6 Nov 2026 (SSVC 2.0.3).

timeline

6 Nov 2026Published
6 Nov 2026CISA SSVC assessment: exploitation none · same day later
6 Nov 2026CVE record last updated · same day later
7 Nov 2026Analysed by vulneraibility.com · 1 day later

how to fix

Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.

references

NVD CVE.org CVE Details Source

2 references in the CVE record: 2 links

Linkaccess.redhat.com /security/cve/CVE-2026-83493
Linkbugzilla.redhat.com /show_bug.cgi?id=2526349

sources

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free