Skip to content

ApplicationsCritical 9.8Patch available

CVE-2022-43781

Command injection RCE in Atlassian Bitbucket Server/Data Center (username handling).

How scary is it?

updated 19 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Public exploit code is out2

    1 Metasploit module.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Drop everything

A working exploit is public. Patch now.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: A working exploit is public (Exploit-DB, Metasploit or Nuclei).2 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 2 products in an affected versionAtlassian Bitbucket Data Center / Atlassian Bitbucket Server

    Atlassian Bitbucket Data Center: before 7.17.12, before 7.21.6, before 7.6.19, before 8.0.5 (+5 more)

    Atlassian Bitbucket Server: before 7.17.12, before 7.21.6, before 7.6.19, before 8.0.5 (+5 more)

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed releasebefore 7.0

    Atlassian Bitbucket Data Center: before 7.0

    Atlassian Bitbucket Server: before 7.0

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenApply vendor update when available; disable public signup; restrict access and monitor logs.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. Atlassian Bitbucket is widely used in enterprises; this RCE via command injection can disrupt orgs and lead to full system compromise, and may be exploitable without auth if public signup is enabled.

CVSS
9.8Criticalscored by CISA
Exploited in the wild
Not knownPublic exploit code; not in CISA KEV
EPSS
98.0%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 21 Nov 2026
Fix
Fixed in before 7.0per the vendor
Published
17 Nov 2022analysed here 19 Nov 2026

Do first. Upgrade to a fixed release: before 7.0.

Summary

Impact

Remote code execution via command injection in username handling; can be unauthenticated if 'Allow public signup' is enabled, leading to arbitrary system command execution.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Atlassian Bitbucket Data Centerbefore 7.17.12before 7.21.6before 7.6.19before 8.0.5before 8.1.5before 8.2.4before 8.3.3before 8.4.2before 8.5.0Vendor says fixed in: before 7.0
Atlassian Bitbucket Serverbefore 7.17.12before 7.21.6before 7.6.19before 8.0.5before 8.1.5before 8.2.4before 8.3.3before 8.4.2before 8.5.0Vendor says fixed in: before 7.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • Atlassian Bitbucket Server
  • Atlassian Bitbucket Data Center

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? Partly. Command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.

Also consider: input validation · RASP

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Yes: 1 Metasploit module
CISA SSVC
exploitation none, automatable yes, technical impact totalAssessed by CISA 2 Oct 2024 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Metasploit

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 17 Nov 2022Published
  2. 2 Oct 2024CISA SSVC assessment: exploitation none686 days (about 2 years) later
  3. 2 Oct 2024CVE record last updatedsame day later
  4. 19 Nov 2026Analysed by vulneraibility.com778 days (about 2 years) later

Common questions

Is CVE-2022-43781 being exploited?

Not confirmed. CVE-2022-43781 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 98% probability of exploitation in the next 30 days.

How severe is CVE-2022-43781?

CVE-2022-43781 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-43781?

Yes. A fix has been recorded for CVE-2022-43781. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2022-43781 affect?

CVE-2022-43781 affects Atlassian Bitbucket Server, Atlassian Bitbucket Data Center. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2022-43781?

Apply vendor update when available; disable public signup; restrict access and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.