CVE-2026-22323
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA CSRF vulnerability in the Link Aggregation configuration interface allows an unauthenticated remote attacker to trick authenticated users into sending unauthorized POST requests to the device by luring them to a malicious webpage. This can silently alter the device’s configuration without the victim’s knowledge or consent. Availability impact was set to low because after a successful attack the device will automatically recover without external intervention.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Cross-Site Request Forgery (CSRF) vulnerability in the Link Aggregation configuration interface of a network device. An unauthenticated remote attacker can craft a malicious webpage that, when visited by an authenticated user, will silently cause the user's browser to send unauthorized POST requests to the device's Link Aggregation settings, allowing configuration changes without the victim's consent.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Link Aggregation interface presenceAccess the network device web management interface and navigate to the Link Aggregation or LACP configuration section. Verify that a configuration interface exists for managing link aggregation groups.Affected if The device has a Link Aggregation configuration interface accessible via HTTP/HTTPS
-
Inspect form for anti-CSRF tokenLog into the device, navigate to Link Aggregation settings, and use browser developer tools to examine the HTML of any POST forms. Look for a hidden input field containing a token value or similar CSRF protection mechanism.Affected if The Link Aggregation configuration forms do not contain a unique, session-bound anti-CSRF token in their submissions
-
Test Origin/Referer header validationSubmit a crafted POST request to the Link Aggregation endpoint using a tool like curl with an altered or mismatched Origin or Referer header. Observe whether the request is rejected or processed.Affected if The device accepts POST requests to Link Aggregation settings from unauthorized origins without validating Origin or Referer headers
-
Check session cookie SameSite attributeUsing browser developer tools or a proxy, inspect the Set-Cookie headers when authenticating to the device. Verify the SameSite attribute value on the session cookie.Affected if The session cookie lacks SameSite=Strict or SameSite=Lax attributes, or uses SameSite=None without Secure
If the Link Aggregation interface lacks anti-CSRF tokens, does not validate Origin/Referer headers, and uses improperly configured session cookies, the device is vulnerable to CVE-2026-22323.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens for all configuration form submissions in the Link Aggregation interface, validate Origin and Referer headers on POST requests, and configure SameSite attributes on session cookies to prevent cross-site request forgery attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22323 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22323 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data