CVE-2026-7219
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 flaw has been found in Totolink N300RT 3.4.0-B20250430. This affects an unknown function of the file /boafrm/formIpQoS. Executing a manipulation of the argument entry_name can lead to buffer overflow. The attack may be performed from remote. The exploit has been published and may be used.
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 confidenceA buffer overflow vulnerability exists in Totolink N300RT router firmware version 3.4.0-B20250430 in the /boafrm/formIpQoS web interface handler. The entry_name parameter is not properly bounds-checked before being used, allowing an attacker to overflow a fixed-size buffer by supplying excessively long input, potentially achieving remote code execution.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify the device modelAccess the router web management interface and check the device information page, or look for 'Totolink N300RT' labeling on the physical device.Affected if The device is not a Totolink N300RT router.
-
Check the installed firmware versionLog into the web management interface and navigate to the firmware or system information page. Look for a version string such as '3.4.0-B20250430' or compare against known Totolink firmware versions.Affected if The firmware version is 3.4.0-B20250430 exactly, or falls within the version range that includes this release.
-
Verify web management interface accessibilityAttempt to access http://[router-ip]/ or https://[router-ip]/ on ports 80 and 443 from a test system. Check if the interface responds to requests.Affected if The web management interface is reachable on the network.
-
Check QoS configuration statusNavigate to the QoS settings page in the web interface (often under 'Advanced' or 'Bandwidth Control' menus). Determine if QoS is enabled or if any QoS rules are configured.Affected if QoS is enabled or any QoS rules exist in the configuration.
A user is affected if they own a Totolink N300RT router running firmware version 3.4.0-B20250430 (or an affected variant) with the web management interface accessible and QoS functionality enabled or configured.
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 dataRestrict network access to the device's management interface immediately. Verify if vendor firmware updates are available; if not, consider network segmentation or device replacement. The published exploit suggests this is remotely exploitable.
- Consultation4.0 h
- Implementation2.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 $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7219 — 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-7219 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