CVE-2026-6133
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 vulnerability was identified in Tenda F451 1.0.0.7_cn_svn7958. This affects the function fromSafeUrlFilter of the file /goform/SafeUrlFilter. Such manipulation of the argument page leads to stack-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might 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 confidenceStack-based buffer overflow in Tenda F451 router firmware 1.0.0.7_cn_svn7958 in the fromSafeUrlFilter function within /goform/SafeUrlFilter. The 'page' parameter is not properly bounds-checked before use, allowing an attacker to overwrite stack memory by providing an oversized input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.0.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device model is Tenda F451Access router web interface or check device label/marketing to verify the exact model number is F451Affected if Device is not a Tenda F451 router, then this specific CVE does not apply
-
Verify firmware version is 1.0.0.7Log into the router admin panel and navigate to System Settings > Firmware Upgrade, or use telnet/SSH and run 'cat /proc/version' or check /etc/version file to identify the installed firmware versionAffected if Firmware version is NOT exactly 1.0.0.7, then the environment is not affected by this specific CVE
-
Confirm web interface is accessibleAttempt to access http://[router-ip]/goform/SafeUrlFilter in a browser or via curl to verify the endpoint respondsAffected if The SafeUrlFilter endpoint is not reachable (e.g., web interface disabled, device not networked), then the attack surface may not be exposed
-
Test 'page' parameter for overflow behaviorSend a crafted request with oversized 'page' parameter (e.g., 500+ characters) to /goform/SafeUrlFilter and observe if the response changes or if unusual behavior occursAffected if The 'page' parameter accepts oversized input without proper bounds-checking, indicating the vulnerability is present and exploitable
The environment is affected only if the device is a Tenda F451 router running firmware exactly version 1.0.0.7, with the web interface accessible and the SafeUrlFilter endpoint exposed to the attacker.
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 dataApply vendor firmware patch when available. Until then, disable or restrict access to the /goform/SafeUrlFilter web endpoint, or isolate the device on a restricted network segment to reduce remote attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6133 — 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-6133 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