PULSE
FEED
ransomvexy ransomware reclama a ZipAI · VN · Technologyransomsilentransomgroup reclama a Smith, Gambrell & Russell, LLP · US · Professional Servicesransomsilentransomgroup reclama a W... R...ransomqilin reclama a Insurance Audit Services · US · Financial Servicesransomn0n reclama a Company #137 · CAransomn0n reclama a Company #136 · DKransomn0n reclama a Company #135 · IDransomn0n reclama a Company #134 · USransomn0n reclama a Company #133 · USransomredact reclama a Omni Hotels & Resorts · US · Hospitalityransomakira reclama a Westboro Partnersransomakira reclama a System Plus · Technologyransomakira reclama a David L Wade & Associates · Professional Servicesransomakira reclama a Source Energy Services · CA · Energy & Utilitiesransomvexy ransomware reclama a ZipAI · VN · Technologyransomsilentransomgroup reclama a Smith, Gambrell & Russell, LLP · US · Professional Servicesransomsilentransomgroup reclama a W... R...ransomqilin reclama a Insurance Audit Services · US · Financial Servicesransomn0n reclama a Company #137 · CAransomn0n reclama a Company #136 · DKransomn0n reclama a Company #135 · IDransomn0n reclama a Company #134 · USransomn0n reclama a Company #133 · USransomredact reclama a Omni Hotels & Resorts · US · Hospitalityransomakira reclama a Westboro Partnersransomakira reclama a System Plus · Technologyransomakira reclama a David L Wade & Associates · Professional Servicesransomakira reclama a Source Energy Services · CA · Energy & Utilities
← All CVEs
CVE WatchNov 5, 2026

CVE-2026-122049

A flaw has been found in Campcodes Bitcoin Wallet System 1.0. This affects the function random_int of the file core/app/Http/Controllers/Aut

CVSS

3.7

Low

EPSS

0.4%

p35

KEV

—

Exploit Today

10

0-100

Published: Nov 5, 2026 · Last modified: Nov 5, 2026 · CWE-307 · CWE-799

EPSS · 30d

Not enough EPSS history yet.

Technical description

A flaw has been found in Campcodes Bitcoin Wallet System 1.0. This affects the function random_int of the file core/app/Http/Controllers/Auth/ForgotPasswordController.php. This manipulation causes improper restriction of excessive authentication attempts. Remote exploitation of the attack is possible. The attack's complexity is rated as high. It is indicated that the exploitability is difficult. The exploit has been published and may be used.

Official references
Related CVEs
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-1221385.3 MED
26.5%
——8BlueprintUE Self-Hosted Edition 4.2.0 before 4.3.4 contains a login rate limit bypass vulnerability in LoginMiddleware.php that keys failed-login counters on case-sensitive usernames. Unauthenticated attackers can vary username casing against case-insensitive MySQL lookups to get extra attempts and brute-force passwords past the per-account lockout.1d
CVE-2026-1197465.9 MED
38.0%
——11ProSoft Technology ICX35 devices (X35-HWC-A and ICX35-HWC-E) contain a login lockout bypass in the integrated module web page. The account lockout mechanism that restricts repeated failed authentication attempts is enforced in client-side JavaScript, so a remote attacker can reset the lockout and continue submitting password guesses by deleting the relevant browser cookies, defeating the brute-force protection. This vulnerability has been addressed in version 1.14.158.1d
CVE-2026-1215353.7 LOW
44.4%
——13A vulnerability was found in miroslavpejic85 MiroTalk P2P up to 2.0.87. This vulnerability affects the function checkPassword of the file app/src/server.js of the component Room Action Handler. The manipulation results in improper restriction of excessive authentication attempts. It is possible to launch the attack remotely. Attacks of this nature are highly complex. It is stated that the exploitability is difficult. The exploit has been made public and could be used. Upgrading to version 2.1.38 is able to resolve this issue. The patch is identified as 55bec1d05f931d2e43633d6d0b7274f79ec719dd. Upgrading the affected component is advised.1d
CVE-2026-118505—
47.7%
——14Improper Restriction of Excessive Authentication Attempts vulnerability in team-alembic ash_authentication allows an unauthenticated attacker to guess passwords and one-time passwords without limit. The password, magic link and OTP strategies enforce brute_force_strategy by adding a preparation only to the actions they generate. When the resource defines one of those actions itself, the strategy uses it as written and nothing checked that it carried the preparation, so the setting compiled and applied no limit. The generators produce exactly this: mix ash_authentication.install writes sign_in_with_password, request_password_reset_token and request_magic_link, mix ash_authentication.upgrade then adds brute_force_strategy to those strategies, and mix ash_authentication.add_strategy.otp writes its OTP actions without the preparation. Separately, with registration_enabled? true the OTP sign-in is a create action, which preparations do not run on, so brute_force_strategy {:preparation, module} never applied to it. This issue affects ash_authentication: from 5.0.0-rc.4 before 5.0.0-rc.16.2d
CVE-2024-56174.8 MED
12.7%
——4The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.3d
CVE-2026-63399—
21.2%
——6Coop is an open source review and moderation tool from ROOST. Prior to 1.0.0, the `GraphQL` `Mutation.createOrg` operation allows an unauthenticated actor to create arbitrary organizations on a publicly accessible instance. In addition to creating noise in the logs, the lack of rate limiting could potentially lead to database exhaustion. Running the service on an authenticated private network prevents outside actors from directly querying the `GraphQL` API. This issue is fixed in version 1.0.0.3d