Is this vulnerability remotely exploitable?

Yes. Any party that is a beneficiary under the affected vesting contracts can exploit the flaw by sending crafted transactions to the blockchain, because smart contracts are inherently remotely callable.

What level of access is required to exploit this issue?

The attacker typically needs to be an address recognized by the vesting contract (for example, a beneficiary or account with a vesting allocation). They do not need privileged off-chain access; the only requirement is the ability to submit on-chain transactions.

What is the safest general fix pattern for this type of bug?

Re-implement vesting logic with explicit, mathematically sound formulas and strict access control, enforce invariants around claimable amounts and timelines, and subject the contract to thorough security review and, where feasible, formal verification before deployment.

Severity:

HIGH RISK

(8.1)

Improper Access Control and Incorrect Vesting Logic (CWE-284, CWE-682) in Token Vesting Contracts for The Graph

CVE-2026-28410

Published:

Mar 5, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Improper Access Control / Logic Error in Smart Contract

CWE:

CWE-284;CWE-682

Impact:

Unauthorized Token Release / Financial Loss

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Access Control / Logic Error in Smart Contract

CWE:

CWE-284;CWE-682

Impact:

Unauthorized Token Release / Financial Loss

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Improper Access Control and Incorrect Vesting Logic (CWE-284, CWE-682) in Token Vesting Contracts for The Graph

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal