Glean Technologies Public Engagement

Description

Glean Responsible Vulnerability Disclosure Glean is an enterprise search and work assistant designed to streamline the process of finding necessary information across various workplace tools such as chat, email, document repositories, bug tracking tools, customer support systems, and internal wikis. It aims to address the challenge of fragmented workplace information, making it easier for teams to accomplish their goals by providing exactly the information needed at the right time. Glean operates by searching all of your apps across your entire company, understanding context, language, behavior, and relationships to find personalized answers to your questions. At Glean we take security very seriously and recognise the value external security researchers bring to the overall security of Glean’s solution. If you believe that you have found a security vulnerability on Glean’s in-scope sites/domains/paths, we encourage you to let us know straight away. We will investigate all legitimate reports and do our best to quickly fix the problem. Before reporting, please review this page including the process and exceptions sections. Ratings/Rewards: For the initial prioritization/rating of findings, this program will use the Bugcrowd Vulnerability Rating Taxonomy . However, it is important to note that in some cases a vulnerability priority will be modified due to its likelihood or impact. In any instance where an issue is downgraded, an explanation will be provided to the researcher - along with the opportunity to appeal, and make a case for a higher priority.

Targets

Testing is only authorized on the targets listed as in scope. Any domain/property of Glean Technologies not listed in the targets section is out of scope. This includes any/all subdomains not listed above. If you happen to identify a security vulnerability on a target that is not in scope, but it demonstrably belongs to Glean Technologies, you can report it to this program. However, be aware that it is ineligible for rewards or points-based compensation. This bounty is part of the Atlassian Marketplace Bounty Program Scope The current scope for security researchers include Glean’s search and assistant. The assistant can be accessed through Glean search. In-scope entry points: Frontend portal: https://app.glean.com/login?qe=https://bug-bounty-be.glean.com&skip_to_sso=1 Backend endpoint: bug-bounty-be.glean.com In-scope paths: Glean dashboard search Everything in the tabs: Directory, Knowledge, Chat New features: HTML Artifacts, Code Writer, File upload, Code interpreter, External Links in Glean Chat. HTML Artifacts: HTML Artifacts is a Glean Canvas feature that allows AI-generated HTML/CSS/JavaScript code to be executed in a sandboxed environment directly within the Canvas interface. Users can ask the LLM to create interactive visualizations, infographics, diagrams (Mermaid charts), and apps, the generated code renders in a sandboxed iframe. Example trigger: Navigate to Glean Chat Ask the assistant to create an HTML artifact, e.g.: "Create an interactive pie chart showing product adoption breakdown" "Show me a Mermaid diagram of our authentication flow in HTML canvas" "Build an interactive calculator" The LLM generates HTML code that executes in a sandboxed preview Users can interact with the rendered content and use actions like "Download as SVG" Code Writer action: Code Writer is an AI‑powered code action in Assistant and Glean Agents that helps debug, edit code, address comments and open draft PRs end‑to‑end with enterprise‑grade security and admin controls, no local setup required. Unlike solutions like Cursor Background tasks, Code Writer runs securely within a customer's dedicated VPC, giving them complete control over data residency and network access. It’s ideal for small/medium features, refactors, tests, and docs, addressing comments work, and can be activated from Assistant, Agents, or Slack. Outcome: Ship small, low‑risk changes faster with fewer handoffs and less context switching. Example trigger: “Update markdown https://github.com/gleanbugbounty/mcp-server-bugbounty/blob/main/CONTRIBUTING.md by replacing every occurence of mise with foo. Create a PR.” File Upload: The file upload feature in Glean Chat allows users to upload various types of files directly from their local computer and query their content in real-time. Here are the key capabilities of the file upload feature: Supported File Formats: Document Files: pdf, doc, docx, pages Spreadsheet Files: xls, xlsx, numbers Presentation Files: ppt, pptx, key Text Files: csv, json, xml, txt Web Files: html, css Code Files: java, py, js, ts, cpp, c, ipynb, sql, sh, go, yaml, log Key Features: File Upload: Users can upload multiple files (up to 5 files, each with a maximum size of 10 MB) directly from their local computer. Real-Time Querying: Users can query the text content of the uploaded files immediately after upload. Document Metadata: The chat UI displays document metadata, such as title and file type. File Deletion: Users can delete uploaded files before submitting their first query. Once a query is submitted, the files cannot be deleted directly from the chat session but will be removed when the chat session history is deleted. Security: Files are parsed and scanned for malware before being stored within the cloud project. Any files with detected malware will have an error for upload. Privacy: Files uploaded will only be accessible to the user who uploaded them. The content of all files uploaded is retained for 24 hours. File metadata is retained for 30 days after a chat session is started and then deleted. Example usage: Upload a pdf and ask Glean to summarise its content. Code Interpreter: The code interpreter in Glean Chat is designed to execute code in a secure, controlled environment, primarily for analyzing structured text files like spreadsheets and CSVs. Here are the key capabilities and features of the code interpreter: Supported File Types: The code interpreter is primarily used for .xls, .xlsx, and .csv files. Key Features: Query Context: The code interpreter is triggered based on the context of the query and the file type. It is used for tasks such as summarization, filtering, calculation, or analysis of the spreadsheet. Text Explanation: After each step of the code interpreter analysis, a text explanation is provided. Intermediate Spreadsheets: Users can view a preview of the spreadsheet and download the generated CSV files. Sandbox Environment: The code interpreter runs in a sandbox environment to ensure security and isolation. Each chat session with a code interpreter invocation is assigned a unique sandbox instance. Example usage: Upload a .csv file containing a series of numbers and ask Glean to perform an arithmetic operation on them. External Links External links feature allows users to submit external URLs as part of a chat message. Glean Chat will be able to fetch the contents of external web links present in the user messages and use them to answer user queries. This feature currently works only in the Public Knowledge app within Glean chat and covers unauthenticated sites with static content (e.g., HTML, PDF, DOCX, PPTX). Example usage: Summarizing news articles Accessing public disclosures, including research and financial disclosures Parsing public APIs and developer documentation New features from 2025-10-31: Code Writer action: Code Writer is an AI‑powered code action in Assistant and Glean Agents that helps debug, edit code, address comments and open draft PRs end‑to‑end with enterprise‑grade security and admin controls, no local setup required. Unlike solutions like Cursor Background tasks, Code Writer runs securely within a customer's dedicated VPC, giving them complete control over data residency and network access. It’s ideal for small/medium features, refactors, tests, and docs, addressing comments work, and can be activated from Assistant, Agents, or Slack. Outcome: Ship small, low‑risk changes faster with fewer handoffs and less context switching. Example trigger: “Update markdown https://github.com/gleanbugbounty/mcp-server-bugbounty/blob/main/CONTRIBUTING.md by replacing every occurence of mise with foo. Create a PR.” Chat Sharing V2 Chat Sharing V2 lets you share a reliable, permission-aware snapshot of a Glean Chat conversation via a link—so others see the same content you saw, without needing to regenerate the chat. It’s designed to be comprehensive, consistent, convenient, and compartmentalized. What it is Frozen, view‑only snapshot of a chat session that preserves the exact messages at the time of sharing, so recipients see the same content as the sharer. Permission-aware redaction: any cited documents/agents the viewer cannot access are redacted or substituted, protecting sensitive information while preserving context. Simple share link flow modeled on familiar assistants; the link is easy to copy and share with teammates. How to use (end users) Open the chat you want to share. Click Share (top-right). The link is generated and easy to copy; a modal lets you adjust who can view. Set permissions to specific people, groups, or organization scope as allowed by admin policy. Viewers get a read‑only snapshot; they cannot edit the original chat. Send the link to recipients. If they lack access to cited sources, those items appear redacted; the answer text remains visible for review. Tip: Use chat sharing when you need colleagues to quickly consume findings, follow the exact steps you used, or review the conversation for decision‑making—without re‑running the session. Known vulnerabilities The following vulnerabilities are not already known and not rewardable(will be considered P5): IDOR in chat sharing to specific people, groups or organization scope. IDOR in snapshot edit by chat recipients. Credentials: How to access and authenticate: Fill the form Access to Glean bug bounty by logging into your google account (gmail) and submit. If you need access to an additional email id, submit the form again from a different google account. You will receive a confirmation email from Google Groups within 24 hours. Check the spam folder if you don't find an email from Google Groups in your inbox. Reach out to [email protected] if you have any questions. Eligible Vulnerability Categories We encourage a coordinated disclosure of the following eligible web application vulnerabilities: Cross-site scripting (XSS) Cross-site request forgery in a privileged context (CSRF) Server-side code execution (RCE) Server-side request forgery (SSRF) XML External Entity Attacks (XXE) SQL Injection (SQLi) Authentication or Authorization flaws including Access Control Vulnerabilities(Insecure Direct Object References issues, etc) Stored Injection Vulnerabilities on client and server side Directory/Path Traversal Information Disclosure Significant Security Misconfiguration LLM related attacks Data exfiltration Insecure output handling with a possible exploitation. Avoid duplicate reports if this is achieved through XSS. Note that third-party applications or websites not owned or controlled by Glean are not within the scope of the program. To receive credit, you must be the first reporter of a vulnerability. When submitting a vulnerability, please provide concise steps to reproduce that are easily understood. Acceptable Criteria for P1 and P2 submissions Should have a valid and reproducible exploit leading to significant loss of business critical data. The final severity will be determined by Glean based on the ease of exploitation and impact. Note: All IDORs in user generated content (Collections, Prompts, Answers, GoLinks, Announcements etc) will be categorised as P4/P5. Rules, Exclusions, and Scopes Any domain/property of Glean Technologies not listed in the targets section is strictly out of scope (for more information please see the out of scope and exclusions sections below). Out-of-Scope Anything not declared as a target or in scope above should be considered out of scope for the purposes of this bug bounty. While we encourage any submission affecting the security of a Glean web property, unless evidence is provided demonstrating exploitability, the following finding types are excluded from this program: Blind XSS must not return any user data that you do not have access to (e.g. Screen shots, cookies that aren't owned by you, etc); when testing for blind XSS, please use the least invasive test possible (e.g. calling 1x1 image or nonexistent page on your webserver, etc). Self-XSS [to be valid, cross-site scripting issues must be exploitable via reflected, stored or DOM-based attacks] Similarly, any XSS where local access is required (i.e. User-Agent Header injection) will not be accepted. The only exception will be if you can show a working off-path MiTM attack that will allow for the XSS to trigger. When testing, please exercise caution if injecting on any form that may be publicly visible - such as forums, etc. Before injection, please make sure your payload can be removed from the site. If it cannot be easily removed, please check with [email protected] before performing the testing. No pivoting or post exploitation attacks (i.e. using a vulnerability to find another vulnerability) are allowed on this program. DO NOT under any circumstance leverage a finding to identify further issues. Any Glean Technologies website (e.g. https://www.glean.com/ ), or any customer domains (e.g. https://customer.glean.com) is out of scope for this bounty unless explicitly included in the scope. Customer cloud instances and data are explicitly out of scope. Any repository that you are not an owner of - do not impact Glean Technologies , or Atlassian customers in any way. Only the latest version of our products are eligible for a reward. Any internal or development services The use of Automated scanners is strictly prohibited (we have these tools too - don't even think about using them) Descriptive error messages (e.g. Stack Traces, application or server errors). HTTP 404 codes/pages or other HTTP non-200 codes/pages. Fingerprinting / banner disclosure on common/public services. Software version disclosure. Disclosure of known public files or directories, (e.g. robots.txt). Clickjacking/UI redressing with no practical security impact. CSRF on forms that are available to anonymous users (e.g. the contact form). CSRF attacks that require knowledge of the CSRF token (e.g. attacks involving a local machine). Open redirects with low security impact (exceptions are those cases where the impact is higher such as stealing OAuth tokens) Logout and other instances of low-severity Cross-Site Request Forgery (logout CSRF) Content spoofing / text injection Cross-site tracing (XST) Presence of application or web browser ‘autocomplete’ or ‘save password’ functionality. Lack of Secure/HTTPOnly flags on non-sensitive Cookies. Lack of Security Speedbump when leaving the site. Weak Captcha / Captcha Bypass. Login or Forgot Password page brute force and account lockout not enforced. Username / email enumeration via Login Page or Forgot Password Page error messages Password and account recovery policies, such as reset link expiration or password complexity OPTIONS HTTP method enabled. Username / email enumeration. Missing cookie flags on non-sensitive cookies. Missing HTTP security headers e.g. Strict-Transport-Security. X-Frame-Options. X-XSS-Protection. X-Content-Type-Options. Content-Security-Policy, X-Content-Security-Policy, X-WebKit-CSP. Content-Security-Policy-Report-Only. Cache-Control and Pragma HTTP/DNS cache poisoning. SSL/TLS Issues, e.g. SSL Attacks such as BEAST, BREACH, Renegotiation attack. SSL Forward secrecy not enabled. SSL weak/insecure cipher suites. No Load testing (DoS/DDoS etc) is allowed on the instance. This includes application DoS as well as network DoS. Vulnerabilities that are limited to unsupported browsers will not be accepted (i.e. "this exploit only works in IE6/IE7"). Known vulnerabilities in used libraries, or the reports that a Glean product uses an outdated third party library unless you can prove exploitability. Missing or incorrect SPF records of any kind. Missing or incorrect DMARC records of any kind. Source code disclosure vulnerabilities. Information disclosure of non-confidential information (e. g. issue id, project id, commit hashes). Methods to extend product trial periods The ability to upload/download viruses or malicious files to the platform. Email bombing/Flooding/rate limiting EXIF Geolocation Data Subdomain takeovers (these are considered P5 at this time) LLM related attacks Prompt injection Jailbreaking Model DoS How to Submit a vulnerability Read these guidelines, ensuring that you follow the process and your vulnerability is in scope. Use the Bugcrowd report a bug process to report vulnerabilities. Every vulnerability report should be unique for a vulnerability. It is mandatory to evaluate the Confidentiality, Availability and Integrity metrics and provide a CVSS v3+ score while submitting a vulnerability report. Responsible Disclosure reporting instructions Your report must include the following information: Contact email address Vulnerability description Vulnerability locations Steps to reproduce and Validation steps Recommended fix Assumed impact Terms & Conditions You give us reasonable time to investigate and mitigate an issue that you report before making any information about the report public or sharing such information with others. You must ensure that customer data is not affected in any way as a result of your testing. Please ensure you're being non-destructive whilst testing and are only testing on instances that you own. In addition to above, customer instances are not to be accessed in any way (i.e. no customer data is accessed, customer credentials are not to be used or "verified") If you believe you have found sensitive customer data (e.g., login credentials, API keys etc) or a way to access customer data (i.e. through a vulnerability) report it, but do not attempt to successfully validate if/that it works. Use of any automated tools/scanners is strictly prohibited and will lead to you being removed from the program (trust us, we have those tools too). Reports need to be submitted in plain text (associated pictures/videos are fine as long as they're in standard formats). Non-plain text reports (e.g. PDF, DOCX) will be asked to be resubmitted in plain text. Grants/awards are at the discretion of Glean Technologies and we withhold the right to grant, modify or deny grants. But we'll be fair about it. Tax implications of any payouts are the sole responsibility of the reporter. Do NOT conduct non-technical attacks such as social engineering, phishing or unauthorized access to infrastructure. Do NOT test the physical security of Glean Technologies offices, employees, equipment, etc. This bounty follows Bugcrowd’s standard disclosure terms. You do not exploit a security issue that you discover for any reason. You do not violate any other applicable laws or regulations. You do not interact with an individual account (which includes modifying or accessing data from the account) without the account owner's explicit consent in writing, which you must produce upon request. You make a good faith effort to avoid privacy violations and disruptions to others, including (but not limited to) unauthorized access to or destruction of data, and interruption or degradation of our services. You must not intentionally violate any applicable laws or regulations, including (but not limited to) laws and regulations prohibiting the unauthorized access to data. If you inadvertently access another person's data or Glean company data without authorisation while investigating an issue, you must promptly cease any activity that might result in further access of user or Glean company data and notify Glean what information was accessed (including a full description of the contents of the information) and then immediately delete the information from your system. Continuing to access another person's data or company data may demonstrate a lack of good faith and disqualify you from any benefit of the Safe Harbour Provisions described below. You must also acknowledge the inadvertent access in any related bug bounty report that you may subsequently submit. You may not share the inadvertently accessed information with anyone else. Not be employed by or a contractor/vendor of Glean or its subsidiaries or affiliates, or be an immediate family member of a person employed by Glean or its subsidiaries or affiliates (defined for these purposes as including spouse, domestic partner, parent, legal guardian, legal ward, child, and sibling, and each of their respective spouses, and individuals living in the same household as such individuals). Please send all reports via report a bug in Bugcrowd. Please note we may only reply to the first reporter of a significant issue. Any reward payments will be made through BugCrowd with no exceptions or alternatives provided. Bug Bounty Process Your submission will be reviewed and validated by Glean’s internal Security Team. Depending upon the severity of your issue, it may take us time to respond to you, please do not contact our staff directly but use the above email contact method instead. When submitting a vulnerability, please provide concise steps to reproduce that are easily understood. If the same vulnerability is found on multiple hosts associated with the same asset/domain, please include all vulnerable hosts in a single report. When duplicates occur, we consider the first report that was received to be treated as unique, and all subsequent reports will be marked as duplicates. (Glean determines duplicates in its sole discretion and is not obligated to share details on prior similar reports.) Report a security bug: identify a vulnerability in our services or infrastructure which creates a security or privacy risk. (Note that Glean ultimately determines the risk of an issue, and that many software bugs are not security issues.) Report the vulnerability upon discovery or as soon as is feasible. Report a security bug involving one of the products or services that are within the scope of the programme; we specifically exclude certain types of potential security issues, listed under “Ineligible Vulnerabilities” below. We may retain any communications about security issues that you report for as long as we deem necessary for programme purposes, and we may cancel or modify this programme at any time. Public Disclosure Before disclosing an issue publicly we require that you first request permission from us. Glean Technologies will process requests for public disclosure on a per report basis. Requests to publicly disclose an issue that has not yet been fixed for customers will be rejected. Any researcher found publicly disclosing reported vulnerabilities without Glean Technologies’s written consent will have any allocated bounty withdrawn and disqualified from the program. Safe Harbor: When conducting vulnerability research according to this policy, we consider this research to be: Authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws), and we will not initiate or support legal action against you for accidental, good faith violations of this policy; Exempt from the Digital Millennium Copyright Act (DMCA), and we will not bring a claim against you for circumvention of technology controls; Exempt from restrictions in our Terms & Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy; and Lawful, helpful to the overall security of the Internet, and conducted in good faith. You are expected, as always, to comply with all applicable laws. If at any time you have concerns or are uncertain whether your security research is consistent with this policy, please create a ticket with Bugcrowd Support for clarification before proceeding.

In Scope Targets (in scope)

Note : Glean (scio) apps in Atlassian marketplace are used internally by Glean to connect with Atlassian data source. The Atlassian marketplace in itself is not in scope of this program. Any submission which is not related to Glean is explicitly out of scope.