Hackerone Reports

🎯 New Report #3621606: ZMQ RPC Log Injection and Untrusted Payload Persistence
🔺Severity: Medium
👽 Reporter: redlobsterzzz
⭐️ Reputation: 107
🛠 State: resolved
💼 Team: Monero
💵 Bounty: null
🕐 Submitted: 2026-03-22
⏰ Disclosed: 2026-07-24 19:19:52
📝 Summary: A vulnerability was reported in the Monero CLI daemon where the ZMQ RPC request path logs untrusted request content before semantic validation. This allowed a remote party with access to the ZMQ endpoint to inject newline and control-character content into daemon logs, enabling log forging. The vulnerability was introduced in commit 77986023c3 and affected releases from v0.12.0.0 through v0.18.4.6, as well as the master branch as of the reported date.
📂 Report JSON File: 3621606
@hackeronereports

🎯 New Report #3641229: GitHub user to server tokens can create issues in any public repository
🔺Severity: Medium
👽 Reporter: ahacker1
⭐️ Reputation: 7438
🛠 State: resolved
💼 Team: GitHub
💵 Bounty: null
🕐 Submitted: 2026-04-01
⏰ Disclosed: 2026-07-22 19:39:24
📝 Summary: A vulnerability was identified in GitHub Enterprise Server that allowed a user-to-server token scoped to a GitHub App installation to perform certain write operations on public repositories outside the token's intended scope. The authorization check only verified that the installation had read permissions on the target repository rather than verifying that the token's installation was explicitly granted access to that repository. This vulnerability was fixed by adding a repository scope check for user-to-server tokens issued by global apps.
📂 Report JSON File: 3641229
@hackeronereports

🎯 New Report #3809407: AWS *.a2z.com | Unauthenticated Clickhouse UI : Database access SSRF
🔺Severity: High
👽 Reporter: notnotnotveg
⭐️ Reputation: 681
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-06-17
⏰ Disclosed: 2026-07-22 19:53:00
📝 Summary: null
📂 Report JSON File: 3809407
@hackeronereports

🎯 New Report #3800870: connect.8x8.com/api/v1: JWT Algorithm Confusion Vulnerability
🔺Severity: High
👽 Reporter: kyotozzx
⭐️ Reputation: 306
🛠 State: resolved
💼 Team: 8x8
💵 Bounty: 1337
🕐 Submitted: 2026-06-13
⏰ Disclosed: 2026-07-22 04:15:44
📝 Summary: A JWT algorithm confusion vulnerability was reported in the v1 API of connect.8x8.com. The JWT verifier did not enforce algorithm pinning and would accept HS256 tokens signed with the RSA public key used as an HMAC secret. The issue was remediated by enforcing RS256 algorithm pinning in the v1 API verifier.
📂 Report JSON File: 3800870
@hackeronereports

🎯 New Report #3588801: OAuth redirect uri validation bypass for :proxima first party sync apps
🔺Severity: High
👽 Reporter: ahacker1
⭐️ Reputation: 7438
🛠 State: resolved
💼 Team: GitHub
💵 Bounty: null
🕐 Submitted: 2026-03-06
⏰ Disclosed: 2026-07-21 21:43:34
📝 Summary: A vulnerability was identified in GitHub Enterprise Server that allowed an attacker to bypass OAuth redirect URI validation. The vulnerability was fixed in versions 3.20.1, 3.19.5, 3.18.8, 3.17.14, 3.16.17, 3.15.21, and 3.14.26. The vulnerability was reported through the GitHub Bug Bounty program.
📂 Report JSON File: 3588801
@hackeronereports

🎯 New Report #3738727: Restricted RPC leaks alternative block hashes via /get alt blocks hashes
🔺Severity: Low
👽 Reporter: int0ha
⭐️ Reputation: 590
🛠 State: resolved
💼 Team: Monero
💵 Bounty: null
🕐 Submitted: 2026-05-15
⏰ Disclosed: 2026-07-20 00:15:10
📝 Summary: The /get alt blocks hashes RPC endpoint was restricted to prevent unintended access to alternative block hashes. The endpoint had previously been unrestricted.
📂 Report JSON File: 3738727
@hackeronereports

🎯 New Report #3779690: Stored XSS in Rocket.Chat HTML File Export — Unauthenticated Entry via LiveChat
🔺Severity: Medium
👽 Reporter: olidayw
⭐️ Reputation: 498
🛠 State: resolved
💼 Team: Rocket.Chat
💵 Bounty: null
🕐 Submitted: 2026-06-03
⏰ Disclosed: 2026-07-16 05:02:04
📝 Summary: A vulnerability was discovered in the HTML file export feature of Rocket.Chat. The vulnerability allowed an attacker to inject arbitrary JavaScript code that would execute when the exported HTML file was opened. The root cause was that the application did not properly sanitize or escape user-supplied data before including it in the exported HTML. As a result, an unauthenticated attacker could leverage the vulnerability to perform actions such as data exfiltration and credential phishing.
📂 Report JSON File: 3779690
@hackeronereports

🎯 New Report #3713965: Able to bypass authorization logic and gain more access then intended
🔺Severity: Medium
👽 Reporter: vaib25vicky
⭐️ Reputation: 2753
🛠 State: resolved
💼 Team: GitHub
💵 Bounty: null
🕐 Submitted: 2026-05-05
⏰ Disclosed: 2026-07-15 16:35:57
📝 Summary: A UI misrepresentation vulnerability was identified in GitHub Enterprise Server that allowed an OAuth application to gain unintended access to an organization's runner management. The vulnerability was fixed in versions 3.21.2, 3.20.4, 3.19.8, 3.18.11, 3.17.17, and 3.16.20. This vulnerability was reported via the GitHub Bug Bounty program.
📂 Report JSON File: 3713965
@hackeronereports

🎯 New Report #3632577: Bedrock AgentCore Starter Toolkit Creates Gateway IAM Roles Without Confused Deputy Protections
🔺Severity: Medium
👽 Reporter: mistercloudsec
⭐️ Reputation: 142
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-03-27
⏰ Disclosed: 2026-07-15 15:11:59
📝 Summary: The Bedrock AgentCore Starter Toolkit was found to create IAM roles for the AgentCore Gateway with trust policies that lacked certain condition keys. This enabled a cross-account confused deputy attack where any AgentCore workload in any AWS account could assume the victim's Gateway role. The role granted access to sensitive resources in the account, including secrets, KMS, Lambda, DynamoDB, and S3.
📂 Report JSON File: 3632577
@hackeronereports

🎯 New Report #3780695: SELECT ... INTO OUTFILE does not enforce the FILE WRITE privilege unprivileged arbitrary file write on the server
🔺Severity: High
👽 Reporter: bisht-ji
⭐️ Reputation: 163
🛠 State: resolved
💼 Team: SingleStore
💵 Bounty: null
🕐 Submitted: 2026-06-03
⏰ Disclosed: 2026-07-13 19:35:07
📝 Summary: A security vulnerability was reported in SingleStore's self-managed database server where the SELECT...INTO OUTFILE command did not properly enforce the FILE WRITE privilege. This allowed any authenticated user, including those with only USAGE privileges, to write arbitrary files to the aggregator host at any path, written as the engine OS user. The vulnerability affected default-configuration self-managed deployments, but was not present in SingleStore Helios due to the local file system access restricted setting. The issue was patched by the vendor and the fix will be reflected in the next patch versions of supported SingleStoreDB releases.
📂 Report JSON File: 3780695
@hackeronereports

🎯 New Report #3702072: bedrock-mantle.api.aws accepts Bedrock API keys outside the IAM Deny, CloudTrail signal, and invocation logging AWS publishes for Bedrock keys
🔺Severity: Medium
👽 Reporter: mistercloudsec
⭐️ Reputation: 142
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-04-28
⏰ Disclosed: 2026-07-14 18:52:27
📝 Summary: A second Bedrock API key-accepting service plane called "bedrock-mantle" was discovered. This plane was not described in AWS's customer-facing Bedrock documentation. As a result, the AWS-published security controls to detect and prevent Bedrock API key abuse failed to apply to the bedrock-mantle plane. Specifically, the IAM deny policy, CloudTrail detection signal, and model invocation logging configuration were all found to be ineffective against the bedrock-mantle plane.
📂 Report JSON File: 3702072
@hackeronereports

🎯 New Report #3581911: Stored XSS on Trix Editor version latest (2.1.16) - Sanitizer Bypass
🔺Severity: Low
👽 Reporter: newbiefromcoma
⭐️ Reputation: 160
🛠 State: resolved
💼 Team: Basecamp
💵 Bounty: 337
🕐 Submitted: 2026-03-02
⏰ Disclosed: 2026-07-14 19:26:37
📝 Summary: A vulnerability was discovered in Trix Editor version 2.1.16 that allowed for a Stored Cross-Site Scripting (XSS) attack. The vulnerability arose from an unsafe interaction between Trix's custom DOMPurify configuration and its document serialization logic. The issue was caused by Trix's use of the "data-trix-serialized-attributes" attribute, which was not properly sanitized during the serialization process, allowing an attacker to inject malicious JavaScript code. The vulnerability was deemed a direct bypass of previously reported Trix Editor vulnerabilities.
📂 Report JSON File: 3581911
@hackeronereports

🎯 New Report #3581911: Stored XSS on Trix Editor version latest (2.1.16) - Sanitizer Bypass
🔺Severity: Low
👽 Reporter: newbiefromcoma
⭐️ Reputation: 160
🛠 State: resolved
💼 Team: Basecamp
💵 Bounty: 337
🕐 Submitted: 2026-03-02
⏰ Disclosed: 2026-07-14 19:26:37
📝 Summary: A vulnerability was discovered in Trix Editor version 2.1.16 that allowed for a Stored Cross-Site Scripting (XSS) attack. The vulnerability arose from an unsafe interaction between Trix's custom DOMPurify configuration and its document serialization logic. The issue was caused by Trix's use of the "data-trix-serialized-attributes" attribute, which was not properly sanitized during the serialization process, allowing an attacker to inject malicious JavaScript code. The vulnerability was deemed a direct bypass of previously reported Trix Editor vulnerabilities.
📂 Report JSON File: 3581911
@hackeronereports

🎯 New Report #3630605: Kiro IDE Stores Auth Tokens with World-Readable Permissions (0644)
🔺Severity: Medium
👽 Reporter: mistercloudsec
⭐️ Reputation: 142
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-03-26
⏰ Disclosed: 2026-07-09 15:31:28
📝 Summary: The Kiro IDE (version 0.11.107) wrote authentication tokens (access token and refresh token) to a file with world-readable permissions (0644). The file contained sensitive information, including the access token, refresh token, and profile ARN. This exposed the credentials to potential unauthorized access by local processes or users.
📂 Report JSON File: 3630605
@hackeronereports

🎯 New Report #3637898: OS Command Injection in `aws-cdk-lib` NodejsFunction via Unsanitized `OsCommand` Helper (Supply Chain RCE)
🔺Severity: High
👽 Reporter: kaporia
⭐️ Reputation: 104
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-03-30
⏰ Disclosed: 2026-07-06 17:48:30
📝 Summary: A vulnerability was discovered in the "aws-cdk-lib" NodejsFunction that allowed for OS command injection through the unsanitized "OsCommand" helper. The vulnerability was caused by the lack of proper escaping of user-controlled data when constructing shell commands during Docker-based bundling. This could have potentially led to arbitrary code execution within the Docker container, which had access to the host filesystem through bind mounts.
📂 Report JSON File: 3637898
@hackeronereports

🎯 New Report #3764217: Any installed app can force immediate logout and persistent DOS of authenticated Basecamp sessions via unprotected exported StartActivity
🔺Severity: Medium
👽 Reporter: zerodaysec xyz
⭐️ Reputation: 201
🛠 State: resolved
💼 Team: Basecamp
💵 Bounty: 287
🕐 Submitted: 2026-05-27
⏰ Disclosed: 2026-07-04 11:05:36
📝 Summary: A vulnerability was discovered in the Basecamp Android app that allowed any installed app to force immediate logout and persistent denial-of-service of authenticated Basecamp sessions. The vulnerability was due to the com.basecamp.bc4.app.main.start.StartActivity being declared as exported without any permission guard. This allowed any app to launch it with an explicit intent, terminating the current session and forcing the user back to the login screen. The behavior was confirmed to be reliable, silent, and persistent.
📂 Report JSON File: 3764217
@hackeronereports

🎯 New Report #3628961: admin.shopify.com: Shopify Flow continues sending internal emails to a configured recipient after the staff author is removed
🔺Severity: None
👽 Reporter: abahack
⭐️ Reputation: 100
🛠 State: informative
💼 Team: Shopify
💵 Bounty: null
🕐 Submitted: 2026-03-26
⏰ Disclosed: 2026-07-03 18:50:06
📝 Summary: null
📂 Report JSON File: 3628961
@hackeronereports

🎯 New Report #3780277: Non-Production API Endpoints for the Amazon S3 Tables Service Fails to Log to CloudTrail Resulting in Silent Permission Enumeration
🔺Severity: Medium
👽 Reporter: nick frichette dd
⭐️ Reputation: 331
🛠 State: resolved
💼 Team: AWS VDP
💵 Bounty: null
🕐 Submitted: 2026-06-03
⏰ Disclosed: 2026-07-02 17:51:21
📝 Summary: A vulnerability was discovered in the Amazon S3 Tables service where certain non-production API endpoints failed to log calls to CloudTrail. This allowed permission enumeration to be performed without leaving any trace in CloudTrail. Twenty-three endpoints were identified that exhibited this behavior, allowing privileged and non-privileged principals to determine the permissions of the accessed identity without generating any CloudTrail events.
📂 Report JSON File: 3780277
@hackeronereports

🎯 New Report #3766455: Yelp for Business: locked Email field silently editable via API
🔺Severity: Medium
👽 Reporter: 0xmanticore
⭐️ Reputation: 449
🛠 State: resolved
💼 Team: Yelp
💵 Bounty: null
🕐 Submitted: 2026-05-28
⏰ Disclosed: 2026-07-02 15:36:44
📝 Summary: The Yelp Biz Android app's Account Information screen was found to have a vulnerability where the email field was presented as read-only with a lock icon, but could be silently modified via the API endpoint POST /account/info/bio/v1. The change was reflected immediately in the app's user interface as well as in the GraphQL API, without any current-password check or out-of-band email confirmation.
📂 Report JSON File: 3766455
@hackeronereports

🎯 New Report #3485343: jitsi-call-analytics: Unauthenticated arbitrary file write via path traversal in `/api/v1/uploads/analyze`
🔺Severity: Low
👽 Reporter: r1skr1der
⭐️ Reputation: 430
🛠 State: resolved
💼 Team: 8x8
💵 Bounty: 100
🕐 Submitted: 2026-01-03
⏰ Disclosed: 2026-07-02 15:41:33
📝 Summary: A path traversal vulnerability was discovered in the /api/v1/uploads/analyze endpoint of the jitsi-call-analytics backend. The vulnerability allowed unauthenticated users to write files within the configured RTCSTATS DOWNLOADS PATH directory. The issue was caused by the upload handler using user-controlled file.originalname directly in path.join() without sanitization, enabling attackers to include ../ sequences to escape the intended per-session UUID directory and write or overwrite files anywhere under the configured root path. The vulnerability was addressed by fixing the security issue in the file upload handler.
📂 Report JSON File: 3485343
@hackeronereports