Bühler Group VDP
By Bühler Vulnerability disclosure program on Intigriti buhlergroup.com
- Top reward
- No cash rewards
- Top severity paid
- Not published
- Assets in scope
- 9
- Public CVEs
- 0
- Last change
At a glance
What to know before you start testing.
- No cash rewards
- A disclosure program: you report for credit, not money.
- Report on Intigriti
- Submit through the program page.
- Full safe harbor
- Good-faith research is authorised; no legal action.
- No public write-ups
- Keep findings private.
Rewards
What Intigriti lists as the payout for each severity.
This program does not pay cash rewards.
- Pays cash
-
No
Although this is a VDP without rewards, we may provide a small bonus in certain circumstances at our discretion:
- Safe harbor
-
Full
Respect the safe harbor clause that you can find below
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
9 assets you may test, 13 excluded.
Wildcard domains 8
- *.buhlercloud.com
- *.buhler-datascience.ch
- *.buhlergroup.ai
- *.buhlergroup.cn
- *.buhlergroup.com
- *.buhlergroup.io
- *.buhlertest.ch
- *.pk-buhler.ch
Networks 1
- 194.9.120.0 - 194.9.123.255
Out of scope (13)
- bestbuy.buhlergroup.com
- channel.buhlergroup.com
- gitlab.buhler-datascience.ch/api/v4/projects
- imap.buhlergroup.cn
- kroki.devops.buhlergroup.com
- pop.buhlergroup.cn
- puml.devops.buhlergroup.com
- smtp.buhlergroup.cn
- *.info.buhlergroup.com
- *.learnhub.buhlergroup.com
- *.virtualworld.buhlergroup.com
- *.virtualworld-portal.buhlergroup.com
- *.webinars.buhlergroup.com
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Bühler Group VDP (via Intigriti)'s policy. "We" in these lines means the program, not this site.
While testing
-
Respect the scope of the program
-
Not to discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube or other platforms)
-
Provide detailed but to-the point reproduction steps
-
Include a clear attack scenario. How will this affect us exactly?
-
Not to use automatic scanners. Be creative and do it yourself! We cannot accept any submissions found by using automatic scanners and which are not proven to cause a security risk
-
Not to obtain, modify, or destroy any information when an identified vulnerability allows you to do so other than to proof the vulnerability
-
Not to perform denial of service or load tests
Not accepted
-
Any submission without a proof-of-concept showing real impact on confidentiality, integrity or availability
-
Any fundamentally existing vulnerability in third party services (such as Microsoft Azure) where no fix is available.
-
Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
-
Spam, social engineering and physical intrusion
-
Missing or insufficient protection against denial of service or brute force attacks including for example identifying orign IP addresses of assets
-
Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
-
Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation
-
Disclosure of non-sensitive information, e.g. in messages/files/directory listings
-
API key disclosure without proven business impact
-
Wordpress usernames disclosure
-
Pre-Auth Account takeover/OAuth squatting
-
Self-XSS that cannot be used to exploit other users
-
Verbose error messages/files/directory listings without disclosing any sensitive information
-
CORS misconfiguration on non-sensitive endpoints
-
Missing cookie flags
-
Missing security headers
-
Cross-site Request Forgery with no or low impact
-
Presence of autocomplete attribute on web forms
-
Reverse tabnabbing
-
Bypassing rate-limits or the non-existence of rate-limits.
-
Best practices violations (password complexity, expiration, re-use, etc.)
-
Clickjacking without proven impact/unrealistic user interaction
-
CSV Injection
-
Sessions not being invalidated (logout, enabling 2FA, changing password, etc.)
-
Missing session fixation - the same account can login from different source systems
Summarised with AI from the program policy on Intigriti, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 17 minutes ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Before we tracked it
Scope and reward changes recorded before this page started tracking it.
-
Scope removed
*.learnhub.buhlergroup.com (out of scope)
-
Scope removed
*.buhlercloud.com
-
Scope removed
puml.devops.buhlergroup.com (out of scope)
-
Scope removed
kroki.devops.buhlergroup.com (out of scope)
-
Scope removed
smtp.buhlergroup.cn (out of scope)
-
Scope removed
imap.buhlergroup.cn (out of scope)
-
Scope removed
channel.buhlergroup.com (out of scope)
-
Scope removed
bestbuy.buhlergroup.com (out of scope)
-
Scope removed
pop.buhlergroup.cn (out of scope)
-
Scope removed
194.9.120.0 - 194.9.123.255
-
Scope removed
*.buhler-datascience.ch
-
Scope removed
gitlab.buhler-datascience.ch/api/v4/projects (out of scope)
-
Scope removed
*.pk-buhler.ch
-
Scope removed
*.buhlertest.ch
-
Scope removed
*.buhlergroup.com
-
Scope removed
*.webinars.buhlergroup.com (out of scope)
-
Scope removed
*.buhlergroup.cn
-
Scope removed
*.virtualworld-portal.buhlergroup.com (out of scope)
-
Scope removed
*.virtualworld.buhlergroup.com (out of scope)
-
Scope removed
*.buhlergroup.io
-
Scope removed
*.buhlergroup.ai
-
Scope removed
*.info.buhlergroup.com (out of scope)
-
Scope removed
194.9.120.0 - 194.9.123.255
-
Scope removed
194.9.120.0 - 194.9.123.255
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
No CVEs matched yet. We match NVD records by vendor name, so products sold under another name can be missing.
Original policy
Copied from www.intigriti.com on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Description
Every day, billions of people come into contact with Bühler technologies to meet their basic needs for food, mobility, and more. Our technologies are in your smartphone, solar panels, diapers, lipstick, banknotes, the food you eat, and the vehicles you drive. We strive to innovate for a better world, with a special focus on healthy, safe, and sustainable solutions. Learn more about Bühler at www.buhlergroup.com.
Rules of engagement
We will:
- Respect the safe harbor clause that you can find below
- Collaborate with you and reply to your submissions as fast as possible
By participating in this program, you agree to:
- Respect the Community Code of Conduct and the Intigriti Terms and Conditions
- Respect the scope of the program
- Not to discuss or disclose vulnerability information without prior written consent (including PoC's on YouTube or other platforms)
- Provide detailed but to-the point reproduction steps
- Include a clear attack scenario. How will this affect us exactly?
- Not to use automatic scanners. Be creative and do it yourself! We cannot accept any submissions found by using automatic scanners and which are not proven to cause a security risk
- Not to obtain, modify, or destroy any information when an identified vulnerability allows you to do so other than to proof the vulnerability
- Not to perform denial of service or load tests
Rewards
Although this is a VDP without rewards, we may provide a small bonus in certain circumstances at our discretion:
- a report is obviously based on a high effort to identify the vulnerability
- a vulnerability is very critical in terms of severity and/or impact to Bühler or our customers
- any other aspect where we think you deserve a reward
We also use the pool of reporters in this VDP as a source for people we potentially invite into our private bug bounty program.
Validation times
We will validate all submissions within the below timelines, once your submission has been verified by Intigriti.
| Severity | Time to validate |
|---|---|
| Exceptional | 2 working days |
| Critical | 5 working days |
| High | 5 working days |
| Medium | 15 working days |
| Low | 20 working days |
In scope
Welcome to Bühler's Vulnerability Disclosure Program! As a company that values security and trust of our customers and business partners, we recognize the importance of preserving the confidentiality, integrity, and availability of sensitive information, and systems. We invite you to contribute to this effort by participating in our VDP.
Our priorities
We are interested in vulnerabilities that effectively and demonstrably impact the security and privacy of our systems or our customers. Examples of what we are specifically looking for include:
- Exposure of personal or otherwise sensitive data
- Privilege escalation / authentication bypass
- SQL injection, remote code execution, cross-site scripting, and the like
We plan to update our scope regularly so keep an eye out or subscribe to our program to receive updates when we do!
Feedback
Would you like to help us improve our program or have some feedback to share, please send your anonymous feedback here: Program feedback link. Please note this form will be checked periodically and must not be used for submission or support queries.
Out of scope
We are interested in real vulnerabilities that have demonstrable impact, not general missing best practices that have no impact on security.
Out-of-scope domains
Any asset/domain not specifically listed in the In Scope section above. For example (third party) domains you see connections to when visiting web applications which serve content or similar.
General
- Any submission without a proof-of-concept showing real impact on confidentiality, integrity or availability
- Any fundamentally existing vulnerability in third party services (such as Microsoft Azure) where no fix is available. Accepted are vulnerabilities which are in our responsibility, for example caused by misconfiguration
- Some websites (partially) share the same codebase. They can contain common issues so if a specific issue has already been found in another website it will not be accepted e.g., for development, integration and production environments
- In case that a reported vulnerability was already known from our own tests or a prior submission, it will be flagged as a duplicate
- Theoretical security issues with no realistic exploit scenario(s) or attack surfaces, or issues that would require complex end user interactions to be exploited
- Spam, social engineering and physical intrusion
- Missing or insufficient protection against denial of service or brute force attacks including for example identifying orign IP addresses of assets
- Attacks requiring physical access to a victim's computer/device, man in the middle or compromised user accounts
- Recently discovered zero-day vulnerabilities found in in-scope assets within 14 days after the public release of a patch or mitigation
- Disclosure of non-sensitive information, e.g. in messages/files/directory listings
- Reports of leaked credentials are not in scope when they do not involve valid application secrets or credentials exposed through an internal issue, misconfiguration, or first-party/in-scope asset. Personal credentials, third-party leaks, credential marketplaces, or leak-monitoring sources may be accepted for awareness.
Application
- API key disclosure without proven business impact
- Wordpress usernames disclosure
- Pre-Auth Account takeover/OAuth squatting
- Self-XSS that cannot be used to exploit other users
- Verbose error messages/files/directory listings without disclosing any sensitive information
- CORS misconfiguration on non-sensitive endpoints
- Missing cookie flags
- Missing security headers
- Cross-site Request Forgery with no or low impact
- Presence of autocomplete attribute on web forms
- Reverse tabnabbing
- Bypassing rate-limits or the non-existence of rate-limits.
- Best practices violations (password complexity, expiration, re-use, etc.)
- Clickjacking without proven impact/unrealistic user interaction
- CSV Injection
- Sessions not being invalidated (logout, enabling 2FA, changing password, etc.)
- Missing session fixation - the same account can login from different source systems
- Tokens leaked to third parties
- Anything related to email spoofing, SPF, DMARC or DKIM
- Content injection without being able to modify the HTML
- Email bombing
- HTTP Request smuggling without any proven impact
- Homograph attacks
- XMLRPC enabled
- Banner grabbing/version disclosure
- Not stripping metadata of files
- Same-site scripting
- Subdomain takeover without taking over the subdomain
- Arbitrary file upload without proof of the existence of the uploaded file
- Blind SSRF without proven business impact (pingbacks are not sufficient)
- Disclosed/misconfigured Google Maps API keys
- Host header injection without proven business impact
- content (e.g. scripts) loaded from third party domains
Infrastructure
- Open ports
- TLS/SSL certificate related issue such as weak ciphers or outdated protocols
- Missing OCSP stapling
Severity
This program follows Intigriti's triage standards. We reserve the right to change the severity rating based on our internal assessments of criticality taking into account the criticality of the system or the involved data. We will explain severity rating changes.
FAQ
Where can I obtain credentials for systems requiring authentication?
At the moment we do not provide credentials for the assets in our VDP scope. You may just focus on black-box testing. However, for systems/services which have a self-service user creation functionality, you may sign-up using your @intigriti.me address.
Why do you exclude so many types of vulnerabilities from the scope?
We already do a lot of automated scanning on all our known (sub)domains. You can assume that most of the "issues" traditional web application security scanners detect are already known to us.