CVE-2026-2378
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 · uneditedArcSearch for Android versions prior to 1.12.7 could display a different domain in the address bar than the content being shown, enabling address bar spoofing after user interaction via crafted web content.
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 · high confidenceAddress bar spoofing vulnerability in ArcSearch for Android allows the browser to display a different domain in the address bar than the actual content being rendered, enabling malicious pages to impersonate legitimate domains after user interaction with crafted web content.
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.12.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
-
Verify ArcSearch for Android is installedCheck your device for the Arc Search app (Thebrowser Arc Search) in your app list or installed applications settingsAffected if ArcSearch for Android is not installed on the device - not affected. If installed, continue to version check.
-
Determine installed ArcSearch versionGo to Android Settings > Apps > Arc Search > App info, or open the Play Store and search for Arc Search to view the installed version numberAffected if Unable to determine version - assume potentially affected if app is present
-
Compare version against affected rangeCompare your installed version number to the affected range: any version below 1.12.7 (such as 1.12.6, 1.12.5, etc.) is within the affected rangeAffected if Installed version is less than 1.12.7 (e.g., 1.12.6, 1.12.0, 1.11.0, etc.) - the device is affected by the address bar spoofing vulnerability
You are affected if ArcSearch for Android is installed and the version is below 1.12.7, as the address bar can display a different domain than the actual content being rendered.
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.
dbcve · scoped1.12.7
Update ArcSearch for Android to version 1.12.7 or later to address the address bar spoofing vulnerability.
1.12.7
- Open the Google Play Store app on your Android device
- Search for "Arc Search" or "Arc Browser"
- Locate the Arc Search application in the search results
- If an update is available, tap the "Update" button to update to version 1.12.7 or later
- Alternatively, navigate to the Arc Search app page in the Play Store and check that the installed version is 1.12.7 or higher
- If automatic updates are enabled, ensure the app has been updated to the latest version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2378 — 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-2378 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